ontology-atlas

Overview Schema Source Related Servers Discussions Admin

connection_info

Read-only

Return the active vault and code-repository roots used by this MCP process, with resolution details. Call first to verify configuration when workspaces or roots may be stale.

Instructions

Return the exact active vault root and code-repository root used by this MCP process, including how each root was resolved. Call first when a client may have stale configuration or multiple workspaces. Root changes require restarting the MCP process. Always returns guide.card, the construction card, plus guide.topics. Pass guide to also receive guideText, the full text of that topic, because a host may truncate the server instructions while tool results arrive whole.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`guide`	No	Return the long-form rules for one topic in `guideText`: `meta_model` (the five authorable kinds and the is_a boundary), `construction` (the rules to read before add_concept), `lifecycle` (review before write), `write_safety` (the dry-run/confirm and expected_mtime patterns), `workflows` (the three starting workflows), or `competency` (the exact `## Competency answers` section `finalize_project_meaning` parses).

Output Schema

TableJSON Schema

Name	Required	Description	Default
`guide`	Yes
`server`	Yes
`repoRoot`	Yes
`sameRoot`	Yes
`guideText`	No
`vaultRoot`	Yes
`repoResolution`	Yes
`vaultResolution`	Yes
`restartRequiredForRootChange`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv1.4.0Oct 1, 2026

changedOutput schema / properties / guide / properties / card / pattern

Previous value: -"^(?!\\s)(?!.*\\s$)(?!.*\\u0000).+$"New value: +"^(?!\\s)(?![\\s\\S]*\\s$)(?![\\s\\S]*\\u0000)[\\s\\S]+$"

changedOutput schema / properties / guideText / pattern

Previous value: -"^(?!\\s)(?!.*\\s$)(?!.*\\u0000).+$"New value: +"^(?!\\s)(?![\\s\\S]*\\s$)(?![\\s\\S]*\\u0000)[\\s\\S]+$"

Changed4 schema fields changedv1.3.0Sep 23, 2026

addedInput schema / properties / guide

Added value: +{
+  "description": "Return the long-form rules for one topic in `guideText`: `meta_model` (the five authorable kinds and the is_a boundary), `construction` (the rules to read before add_concept), `lifecycle` (review before write), `write_safety` (the dry-run/confirm and expected_mtime patterns), `workflows` (the three starting workflows), or `competency` (the exact `## Competency answers` section `finalize_project_meaning` parses).",
+  "enum": [
+    "meta_model",
+    "construction",
+    "lifecycle",
+    "write_safety",
+    "workflows",
+    "competency"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / guide

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "card": {
+      "minLength": 1,
+      "pattern": "^(?!\\s)(?!.*\\s$)(?!.*\\u0000).+$",
+      "type": "string"
+    },
+    "topics": {
+      "items": {
+        "minLength": 1,
+        "pattern": "^(?!\\s)(?!.*\\s$)(?!.*\\u0000).+$",
+        "type": "string"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "card",
+    "topics"
+  ],
+  "type": "object"
+}

addedOutput schema / properties / guideText

Added value: +{
+  "minLength": 1,
+  "pattern": "^(?!\\s)(?!.*\\s$)(?!.*\\u0000).+$",
+  "type": "string"
+}

changedOutput schema / required

Previous value: -[
-  "vaultRoot",
-  "repoRoot",
-  "vaultResolution",
-  "repoResolution",
-  "sameRoot",
-  "restartRequiredForRootChange",
-  "server"
-]New value: +[
+  "vaultRoot",
+  "repoRoot",
+  "vaultResolution",
+  "repoResolution",
+  "sameRoot",
+  "restartRequiredForRootChange",
+  "server",
+  "guide"
+]

First observedv0.13.0Sep 11, 2026

TDQS

A4.6/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already cover the safety profile (readOnly, not destructive), and the description adds real behavioral context beyond them: root changes require restarting the MCP process, the return shape is always guide.card plus guide.topics, and it explains the host-truncation rationale for the guideText path. This is information an agent could not get from the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core return values, then usage, then the optional parameter. Every sentence carries information, though it is dense and could be split slightly more cleanly. No filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present the description needn't enumerate return values, yet it still summarizes the guaranteed fields (guide.card, guide.topics) and the optional guideText. Combined with the restart constraint and the stale-config call trigger, an agent has everything needed to invoke it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with a rich enum description, so the schema carries most of the load (baseline 3). The description adds genuine value by explaining why to pass `guide` – it returns guideText, the full topic text, because hosts may truncate the server instructions while tool results arrive whole. That is semantics beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Return') and resource ('the exact active vault root and code-repository root used by this MCP process'), with the added scope of 'how each root was resolved'. No sibling tool deals with connection roots, so it is clearly distinguishable from the 30+ other tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit when-to-call guidance: 'Call first when a client may have stale configuration or multiple workspaces.' It also notes the restart prerequisite for root changes, which is a usage constraint. It does not name a direct alternative, but none is needed for a diagnostic tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.