build_source_pack
Build Source Pack
Build the source pack for an artifact: a deterministic, sorted extract of the types, elements, taxonomies and relations in scope, plus a stamp with its packHash. Write the artifact only from this pack, then call check_grounding with the pack, the stamp and your output. The packHash is the version pin. Read-only; nothing is stored.
输入参数spaceIdtypeIdstemplateId必填graphProjectId必填provenanceNote
check_artifact_freshness
Check Artifact Freshness
Check whether an artifact is still current. Rebuilds the source pack for the same template and scope and compares its hash with the packHash the artifact was built from. state is current or stale. Pass the old pack too to get a diffSummary of what changed. Read-only.
输入参数packspaceIdtypeIdspackHash必填templateId必填graphProjectId必填
check_grounding
Check Grounding
Check an artifact output against its source pack (closed world). Every name in output.refs, every *Ref / *Refs value, every `backticked` name and every first cell of a table row must exist in the pack. Returns passed, checked, unresolved [{name, where}] and warnings. If it fails, fix only the listed names (one repair attempt is recommended) and check again. Pass the stamp to prove the pack was not modified. Read-only.
输入参数pack必填stampoutput必填graphProjectId必填
diff_source_packs
Diff Source Packs
Compare two source packs by id: types, elements, taxonomy terms and relations that were added, removed or changed. Use it as the basis of a change report. Read-only.
输入参数toPack必填fromPack必填graphProjectId必填
list_artifact_templates
List Artifact Templates
List the artifact templates (data dictionary, model map, change report, ...). Each template has a family, audiences, formats, a pack recipe and an output contract. Your response for an artifact must follow its output contract; pass includeContract: true to get it. Read-only.
输入参数familyaudiencegraphProjectId必填includeContract
render_artifact
Render Artifact
Render a grounded artifact output to text with a provenance footer (templateId, packHash, graphProjectId, builtAt, renderedAt). Formats: md (sections in contract order), mermaid (class diagram drawn from the pack; model-map only), json. With pack and no output, md and mermaid render in degraded mode (no model needed). xlsx, docx and pptx are not supported yet. Read-only; nothing is stored.
输入参数packstamp必填format必填outputtemplateId必填graphProjectId必填
Export project data as an Avro (.avsc JSON) schema string.
输入参数nodeIdsspaceIdgraphProjectId必填
analyze_concept_impact
Analyze Concept Impact
Answers 'what is affected if this concept changes?' for a governed type, element or controlled vocabulary. Returns: where it is used inside the model (blast radius), which vendor estates carry it and by what path, which external standards it is bound to, and which serializations it can be exported as. Read-only — nothing is modified. Useful before editing a vocabulary term or a column's meaning.
输入参数spacesconcept必填graphProjectId必填
audit_vendor_project
Audit Vendor Project
Audits vendor artifacts (e.g. a dbt manifest) against the governed CoreModels graph — read-only. Reports coverage (what is/isn't governed, canonical-mapping coverage), drift (fields added/removed/retyped, enum changes, contract flips), and conformance (vendor best-practice rules). errorCount > 0 is the CI-gate fail signal; 'markdown' holds the human-readable report.
输入参数spacesvendor必填artifactsartifactUrlsgraphProjectId必填
generate_vendor_artifacts
Generate Vendor Artifacts
Generates vendor artifacts from the governed CoreModels graph. For dbt: a schema.yml with enforced model contracts — column data types, not_null/unique constraints and tests, accepted_values tests from governed taxonomies, relationships tests from governed references. SMEs change meaning once in CoreModels; engineers get a reviewed contract diff.
输入参数layoutspacesvendor必填typeNamestargetVersiongraphProjectId必填iriInDescription
get_vendor_integration_status
Vendor Integration Status
Lists the registered vendor connectors (dbt, ...) with capabilities and expected artifacts, and — when 'vendor' is given — the project's last-import state for that vendor (when, tool version, artifact versions, fingerprint, counts, governed dataset count).
输入参数spacesvendorgraphProjectId必填
export_json_ld
Export JSON-LD
Export project data in JSON-LD format using a configured export profile.
Use `fetch_json_ld_import_profiles` first to discover the configTypeId. At least one of exportTypes/exportElements/exportTaxonomies/exportDataTypes must be true. Tree-based mode (graphBased=false) requires exactly one nodeId; graph-based mode allows multiple or none.
输入参数nodeIdsspaceIdgraphBasedexportTypesconfigTypeId必填includeSpaceexportElementsgraphProjectId必填useDefaultTypeexportDataTypesexportTaxonomies
fetch_json_ld_import_profiles
Fetch JSON-LD Import Profiles
Fetch JSON-LD import/export profiles available for a project (id and label each).
Pass configTypeId to read that one profile's field mapping instead: every JSON-LD key it knows and what the key imports as - importAs is mixin (target = mixin column id), relation (target = relation group id), newMixin/newRelation (created on import), space, or none (ignored). targetLabel names the mixin column or relation group; isReversed marks a relation read in the opposite direction.
输入参数configTypeIdgraphProjectId必填
export_jsonschema
Export JSON Schema
Export project data as a JSON Schema string.
输入参数spaceIdrootNodeIdconfigTypeIdgraphProjectId必填
fetch_json_schema_import_profiles
Fetch JSON Schema Import Profiles
Fetch JSON Schema import/export profiles available for a project (id and label each).
Pass configTypeId to read that one profile's field mapping instead: every JSON Schema keyword it knows and what the keyword imports as - importAs is mixin (target = mixin column id), relation (target = relation group id), newMixin/newRelation (created on import), space, or none (ignored). targetLabel names the mixin column or relation group; isSpecialKey marks a structural JSON Schema keyword (properties, items, $ref, ...).
输入参数configTypeIdgraphProjectId必填
validate_json
Validate JSON
Validate one or more JSON documents against a project's stored JSON Schema.
The schema is regenerated from the project using the supplied configTypeId (the export profile id) and rootNodeId, then reused for every document - so validating a batch costs barely more than validating one. Pass up to 100 documents per call and chunk anything larger.
Response:
- isValid: true only when EVERY document passed.
- total, validCount: counts over the whole batch.
- invalid: one entry per failing document, as {index, errors}. Only failures are listed - any index not present passed. index is the 0-based position in the jsonStrings array you sent.
- A document that is not parseable JSON fails in its own slot; it does not abort the rest of the batch.
Set explain=true to add a plain-English "- Explanation:" line to every error, describing what is wrong, where, and how to fix it. The raw structured lines are unchanged either way - use it when a person will read the result, leave it off for machine parsing.
输入参数explainspaceIdrootNodeId必填jsonStrings必填configTypeIdgraphProjectId必填
export_linkml
Export LinkML
Export project data as a LinkML (YAML) schema string.
输入参数nodeIdsspaceIdgraphProjectId必填
get_job_status
Get Job Status
Get the status of a background job in a project, e.g. the copy started by copy_project or a background import_owl. Returns { jobDetailsId, projectId, type, status, createdAt, lastUpdatedAt } where status is "inProgress", "success" or "failed". Result-bearing jobs (background import_owl) additionally return a 'result' field on success — for OWL imports it carries the type/element/taxonomy counts and the aggregated lossiness. Poll until status is no longer "inProgress"; leave a few seconds between polls.
输入参数jobDetailsId必填graphProjectId必填
get_mixins_and_relation_groups
Get Mixins & Relation Groups
Get the project schema: all mixin definitions and all relation-group definitions.
Use this once at the start of a session to discover the IDs needed by other tools (mixinId, columnId, relationGroupId). Returns compact positional arrays - see the "format" field for the layout.
Read get_modeling_guide before your first write - it explains what each relation group means and which direction it runs.
输入参数graphProjectId必填
get_modeling_guide
Get Modeling Guide
Returns the CoreModels modeling guide (markdown): how to import vs build, what each relation group means and which direction it runs (Domain Includes, Range Includes, Controlled List, Has List Item, Inheritance, Derived From), bulk_create conventions, and how to verify your work. Read it once before your first write in a session.
无需输入参数。
get_project_summary
Get Project Summary
Labels and IDs of types, elements, and taxonomies in the project. Each category is paginated independently.
Pagination:
- First call: omit page (defaults to 0).
- Each category reports page, pageSize and hasMore. Re-request with page+1 for any category whose hasMore is true.
输入参数pagepageSizegraphProjectId必填
list_projects
List Projects
List the user's CoreModels projects as [id,name,accessLevel] (see the response "format" field). Use a returned id as graphProjectId for other tools. Pass searchTerm to filter by name (case-insensitive substring). Set includePublicProjects=true to also include public projects. Set includeAISummary=true to also return each project's saved AI-generated summary and the time it was generated (4th and 5th elements). Paged: page is 1-based; increment page up to the returned totalPages to get all results.
输入参数pagepageSizesearchTermincludeAISummaryincludePublicProjects
core_models_get_mixins_info
Core Models Get Mixins Info
Get information about all mixins in a CoreModels project.
Mixins define structured metadata used for mapping models, system integrations, and other extensions.
Mixin values are attached to nodes; use search_nodes with includeMixins to see them, and bulk_create or create_mixin_value to set them.
输入参数graphProjectId必填
query_model_graphql
Query Model Graphql
Run a read-only GraphQL query against a CoreModels project's model — the general query escape hatch for precise questions (projections, traversals, counts) that the fixed read tools don't answer. Viewer access is required, same as the app.
The schema is GENERATED PER PROJECT: field names are camelCased from this project's labels and cannot be guessed. Always call with schemaOnly=true first and write queries against the returned SDL (standard introspection queries also work, but the SDL is far cheaper). Root fields: types, elements, taxonomies, views, exemplars, spaces, mixins, relationGroups. Node roots take filter arguments id, ids, names, spaceId — note `names` is a search expression, not an exact match.
Queries only: the schema has no Mutation or Subscription type. GraphQL variables and operationName are not supported — inline all literals into the query document.
There is NO pagination and every matched node is returned with all its relations, so select narrowly and always filter. Results whose serialized data exceeds maxChars come back as { truncated: true, totalChars, maxChars, dataPreview } instead of { data } — tighten the query rather than raising maxChars. On a GraphQL error (usually a wrong field name) you get an error result; re-check the schema with schemaOnly=true.
输入参数querymaxCharsschemaOnlygraphProjectId必填
core_models_get_relation_groups_info
Core Models Get Relation Groups Info
Get information about relation groups for a CoreModels project.
Use the relation groups to create a relation between two nodes.
输入参数graphProjectId必填
Search nodes in a CoreModels project. Returns compact positional arrays; the response "format" field describes the layout.
Filters (provide at least one of the first three; they combine with AND):
- nodeIds: exact id lookup
- nodeType: one of Element, Type, Taxonomy, Exemplar, Component, Space, Tag, Mixin
- expression: partial substring match on the node label (plain text, no wildcards)
- spaceIds: restrict results to specific spaces. Narrowing only - cannot be the sole filter; always combine it with nodeIds, nodeType, or expression.
Optional flags: includeRelations, includeMixins, includeTimestamps, sortAttr, sortDesc, pageSize.
Pagination:
- Page-number based: pass page (1-based) and pageSize (max 250).
- The response includes the total match count, so more pages exist while page * pageSize < total.
输入参数pagenodeIdsnodeTypepageSizesortAttrsortDescspaceIdsexpressionincludeMixinsgraphProjectId必填includeRelationsincludeTimestamps另有 1 个
Who is calling: returns the identity and subscription plan of the MCP token in use. No project id needed.
Returns { userId, name, email, organizationId, plan }. plan holds the raw tier and expiry from the token plus the derived limits and permissions the other tools enforce: canWrite (writes allowed at all), sharingAllowed (whether invite_user will work — the app's Share-button rule), isEnterprise (large-project copies), maxProjects and maxNodesPerProject. limitsEnforced reports whether the project-cap and per-project node-cap are currently applied on MCP calls (auto-activates 2026-12-31; sandbox project 8185f7b2bd254d1496c6388cd7dc26e6 exempt). Call it at the start of a session to know your limits before creating or importing.
无需输入参数。
suggest_ontology_terms
Suggest Ontology Terms
Suggest ontology-term candidates for a schema node from the public EMBL-EBI Ontology Lookup Service
(OLS). ADVISORY ONLY: this is a read-only search — it calls the external EBI OLS API and returns
ranked candidates, and it NEVER writes anything to the graph. In particular it never sets the
authoritative mapsTo mixin; binding a chosen term is a separate, explicit human-directed act via
bind_ontology_term (you name the exact node and the exact term IRI).
Provide either nodeId (the node's label is used as the query) or a raw label (optionally with a
description). Optionally restrict to a comma-separated list of ontologies (e.g. "efo,mondo,hp") and
cap the number of candidates. Each candidate carries { iri, curie, label, description, ontology, type }
in the relevance order OLS returns; the iri is what you would pass to bind_ontology_term.
输入参数labellimitnodeIdontologiesdescriptiongraphProjectId必填
Export project data as a ShEx (Shape Expressions) schema string.
输入参数nodeIdsspaceIdgraphProjectId必填includeCardinality
Export project data as a SQL DDL (CREATE TABLE) schema string.
输入参数nodeIdsspaceIdgraphProjectId必填
export_owl
Export OWL (Turtle)
Export project schema as an OWL ontology (Turtle): owl:Class per Type, Datatype/ObjectProperty per
Element with domain/range, rdfs:subClassOf inheritance, cardinality restrictions preserving
required/array-ness, SKOS concept schemes per Taxonomy, and owl:equivalentClass/Property from
cross-standard mappings. Anything OWL cannot express is reported as '# lossiness:' comments at the
top of the document instead of being silently dropped.
输入参数spaceIdgraphProjectId必填
export_rml
Export RML mapping (Turtle)
Export the project as an RML mapping document (RML-Core + RML-IO, namespace http://w3id.org/rml/):
one rml:TriplesMap per Type, an rml:logicalSource per source file or table, a subject template from
the identifier element, one rml:predicateObjectMap per Element, and joins (rml:parentTriplesMap +
rml:joinCondition) for type references. Run the result in an RML engine (RMLMapper, morph-KGC,
SDM-RDFizer) to build a knowledge graph from your data.
Give sourceKind to bind it to real data (csv | json | xml | sql | sql-query); omit it for a
skeleton with placeholder sources. The document's first line states its fidelity: RUNNABLE,
TEMPLATE or SKELETON.
Class and predicate IRIs come from each Type's and Element's mapsTo binding. Where a term is not
bound, the IRI is minted from its name and reported as '# lossiness:' — a mapping built on minted
IRIs produces a graph that joins to nothing, so bind the terms (bind_ontology_term) before
publishing the output.
输入参数baseIrispaceIdsourceFormsourceKindgraphProjectId必填sourceTemplate
generate_synapse_manifests
Generate Synapse Manifests
Generate Synapse curation-manifest CSV templates from a schema — the tabular companion to the
transform_schema synapse export. Two artifacts per type: {name}.manifest.csv (the blank entry grid,
header row only, loadable as a Curator RecordSet CSV) and {name}.dictionary.csv (the column
dictionary: Column, Type, Description, Required, Value Set — followed by a value-set section listing
taxonomy terms for dropdown columns). Source formats: jsonschema | shex | avro | jsonld | sql | osi |
osi-json | owl | linkml | odm. Stateless — the project scopes auth only; nothing is written.
输入参数typeIdsourceFormat必填sourceSchema必填graphProjectId必填
transform_schema
Transform Schema
Transform a schema from one format to another through the ARAMAI mapping engine.
Formats: jsonschema | shex | avro | jsonld | sql | osi | osi-json | owl | linkml | protobuf | odcs | graphql | odm | synapse
(odm decodes only; osi-json is the OSI coder in its JSON serialization — the form dbt ingests;
synapse encodes only — the Sage Bionetworks Synapse draft-07 subset with a registered-schema $id;
its output is plain JSON Schema, decodable via jsonschema; protobuf is a single proto3 .proto file,
alias proto; odcs is a Bitol Open Data Contract Standard v3 YAML data contract; graphql is a GraphQL
SDL type-system document, alias sdl — the universal fallback for importing any CMS content model,
since every headless CMS can emit an SDL schema; decode imports the content model and skips the
generated query surface — root operation types, Connection/Edge/PageInfo pagination, filter inputs —
with an honest lossiness summary).
Mapping: 'inferred' (label/type matching against a target hint), 'explicit' (a SIA mapping-guide
JSON: autoMatchByMapsTo, fieldMappings [{sourceElementIds, targetElementIds, transformName}],
taxonomyDirectives, drops), or 'ai' (Claude proposes a plan; the same validation gate accepts or
rejects it — requires a server-configured Anthropic key and Editor/Admin project membership, and
sends the schemas to the Anthropic API server-side). The response carries the produced schema,
the executed plan (replayable), and an honest lossiness ledger of everything the transformation
could not preserve.
输入参数guidevendorsynapseOrgmappingKindsynapseNamesourceFormat必填sourceSchema必填targetFormat必填graphProjectId必填synapseVersioncaseInsensitivetargetHintFormat另有 1 个
schema_library_query_project
Schema Library Query Project
Query and retrieve details of a SchemaLibrary project including metadata, classifications, likes, cover images, and user permissions. Authenticated callers receive additional user-specific data (e.g. ILiked, Role).
输入参数projectId必填
schema_library_get_metadata_options
Schema Library Get Metadata Options
Get available metadata options for SchemaLibrary projects (access methods, types, licenses, formats, domains, audiences, model sizes). Use these IDs when creating or updating projects. Optionally filter by category.
输入参数category
schema_library_get_classifications
Schema Library Get Classifications
Get available classification options for SchemaLibrary projects, used to categorize and tag projects. Optionally filter by classification name (partial match supported).
输入参数nameFilter
schema_library_projects_section
Schema Library Projects Section
Search and retrieve a filtered, paginated list of SchemaLibrary projects with advanced filtering options including metadata, classifications, and project attributes.
输入参数pagetitlesortBytypeIdpageSizedomainIdsformatIdslicenseIdisExternalisFeaturedaudienceIdsmodelSizeId另有 7 个
schema_library_get_use_case_types
Schema Library Get Use Case Types
Get available use case types for SchemaLibrary projects. Use these types when creating new use cases for a project.
无需输入参数。
Execute a JavaScript program that orchestrates this server's tools, and return only its result.
Prefer this over many individual tool calls when a task needs several steps, looping, filtering, or
combining data: intermediate results stay in the sandbox, so only what you return reaches the model.
Inside the script:
- listTools() -> [{name, summary}] discover available tools
- getToolDoc(name) -> {name, description, parameters, required} inspect one tool's inputs
- tools.<name>(args) -> parsed result call a tool (graphProjectId is injected automatically; do NOT pass it)
- console.log(...) captured and returned alongside the result
- return <value> JSON-serialized and returned
Environment: sandboxed JavaScript, no network or filesystem, with limits on time, memory, statements
and number of tool calls.
This endpoint serves read-only tools, so only read tools are ever callable from code here. Code-mode
writes (an allowlist of creation tools) are served by the admin endpoint (/mcp-admin).
Use listTools() to see what is callable right now.
输入参数code必填dryRungraphProjectId必填