CoreModels

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

Fetch JSON-LD import/export profiles available for a project.

Export project data as a JSON Schema string.

Fetch JSON Schema import/export profiles available for a project.

Imports a JSON Schema into a space

Validate a JSON document against a project's stored JSON Schema. The schema is regenerated from the project using the supplied configTypeId (the export profile id) and rootNodeId. Provide the JSON to validate as a serialized string.

Create multiple nodes, relations, and mixin values in one atomic operation. When to use: - Creating more than one node. - Any creation that includes relations and/or mixins. - For a single node with no relations/mixins, prefer create_node. Required ids come from: - get_mixins_and_relation_

Create a new mixin type. Check existing mixins first with get_mixins_and_relation_groups to avoid duplicates. Mixins are reusable property sets applicable to any node.

Create a new CoreModels project owned by the calling user, including a ready-to-use default space. Returns { projectId, defaultSpaceId }; use projectId as graphProjectId and defaultSpaceId as a spaceId in other tools (e.g. import_jsonschema). Projects are created private in the caller's default work

Generate an AI summary of the project (from its types, elements and taxonomies) and save it as the project's markdown AI summary. Returns the generated summary. If a summary already exists it is returned unchanged unless regenerateIfStale=true (default) and the project has been updated since the sum

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.

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.

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=tr

Create a mixin value for a node. mixinId and column ids come from get_mixins_and_relation_groups. A node can have multiple mixins; each mixin can have multiple columns.

Remove one or more mixin column values from a node. mixinId and column ids come from get_mixins_and_relation_groups. This does not delete the mixin definition itself.

Create a new node. Empty/omitted spaceIds = default space; MUST be empty when nodeType is 'Space'.

Update an existing node's label and/or its space assignments. Omitted fields are unchanged. spaceIds replaces (not merges) existing assignments; empty array = default space. At least one of label or spaceIds must be provided.

Suspend a node.

Create a directed relation fromNodeId → toNodeId. relationGroupId is the relation template; list templates with get_mixins_and_relation_groups.

Remove a relation between two nodes.

Search nodes in a CoreModels project. Returns compact positional arrays; the response "format" field describes the layout. Filters (provide at least one; they combine with AND): - nodeIds: exact id lookup - nodeType: one of Element, Type, Taxonomy, Exemplar, Component, Space, Tag, Mixin - expr

Export project data as a ShEx (Shape Expressions) schema string.

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.