Agentic Atlas

Read an Atlas Node, Section, Decision, or Term

atlas_read

Read-onlyIdempotent

Read the full text at one exact Atlas address. A bare Node id returns the whole entry: identity, tree position, Hook (one-line summary), and every Section; relationship occurrences are omitted. A Section, Decision, or glossary term address returns that one item. Use when a summary is not enough or you need exact wording to cite. An unknown or malformed address is refused as invalid_argument; a wrong slug's refusal lists the real ones.

Input Schema

Name	Required	Description	Default
`address`	Yes	A bare Node id, 'node-id#section-slug', 'decision:<decision-id>', or 'term:<key>'. Slugs are not guessable: read them off a Node's sections, a Card claim's sources, or a Link's occurrence.
`expected_revision`	No	Pins this call to the Release (published edition) a prior payload named in 'coherence'; refused as 'revision_changed' if the active Release has changed. Omit for the active Release.

Output Schema

Name	Required	Description
`data`	Yes	node: identity (id, title, kind), hierarchy (ancestors, sibling_position, sibling_count), hook, and sections (slug, heading, position, content). section: section. decision: decision (id, title, content). definition: term and definition.
`scope`	Yes
`coherence`	Yes
`projection`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 20, 2026
- changedOutput schema / properties / projection / const
```
Previous value: -"agent-projection/v7"New value: +"agent-projection/v8"
```

Changed4 schema fields changedOct 18, 2026

changedOutput schema / properties / data / description

Previous value: -"node: identity (id, title, kind, status), hierarchy (parent, ancestors, breadcrumb, sibling_position, sibling_count), hook, and sections (slug, heading, position, content). section: section. decision: decision (id, title, content). definition: term and definition."New value: +"node: identity (id, title, kind), hierarchy (ancestors, sibling_position, sibling_count), hook, and sections (slug, heading, position, content). section: section. decision: decision (id, title, content). definition: term and definition."

removedOutput schema / properties / payload_class

Removed value: -{
-  "enum": [
-    "section",
-    "node",
-    "definition",
-    "decision"
-  ],
-  "type": "string"
-}

changedOutput schema / properties / projection / const

Previous value: -"agent-projection/v6"New value: +"agent-projection/v7"

changedOutput schema / required

Previous value: -[
-  "projection",
-  "coherence",
-  "payload_class",
-  "scope",
-  "data"
-]New value: +[
+  "projection",
+  "coherence",
+  "scope",
+  "data"
+]

Changed3 schema fields changedOct 16, 2026

changedInput schema / properties / address / description

Previous value: -"A bare node id; 'node-id#section-slug', the slug read off a Node's sections, a Card claim's sources, or a Link's occurrence (slugs are not guessable); or 'decision:<decision-id>'; or 'term:<key>'."New value: +"A bare Node id, 'node-id#section-slug', 'decision:<decision-id>', or 'term:<key>'. Slugs are not guessable: read them off a Node's sections, a Card claim's sources, or a Link's occurrence."

changedInput schema / properties / expected_revision / anyOf

Previous value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "pattern": "^v\\d+\\.\\d+\\.\\d+$",
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

changedInput schema / properties / expected_revision / description

Previous value: -"The Release version a prior payload returned as 'coherence', pinning this call to it; 'revision_changed' refuses a moved Release. Omit to read the active Release."New value: +"Pins this call to the Release (published edition) a prior payload named in 'coherence'; refused as 'revision_changed' if the active Release has changed. Omit for the active Release."

Changed2 schema fields changedOct 16, 2026

changedInput schema / properties / expected_revision / description

Previous value: -"A prior payload's 'coherence'; 'revision_changed' refuses a moved Release."New value: +"The Release version a prior payload returned as 'coherence', pinning this call to it; 'revision_changed' refuses a moved Release. Omit to read the active Release."

addedOutput schema / properties / data / description

Added value: +"node: identity (id, title, kind, status), hierarchy (parent, ancestors, breadcrumb, sibling_position, sibling_count), hook, and sections (slug, heading, position, content). section: section. decision: decision (id, title, content). definition: term and definition."

Changed3 schema fields changedSep 7, 2026

changedInput schema / properties / address / description

Previous value: -"A bare node id; 'node-id#section-slug', the slug read off a Node's sections, a Card claim's sources, or a Link's occurrence (slugs are not guessable); or 'decision:<decision-id>'."New value: +"A bare node id; 'node-id#section-slug', the slug read off a Node's sections, a Card claim's sources, or a Link's occurrence (slugs are not guessable); or 'decision:<decision-id>'; or 'term:<key>'."

changedOutput schema / properties / payload_class / enum

Previous value: -[
-  "section",
-  "node",
-  "decision"
-]New value: +[
+  "section",
+  "node",
+  "definition",
+  "decision"
+]

changedOutput schema / properties / projection / const

Previous value: -"agent-projection/v5"New value: +"agent-projection/v6"

Changed1 schema field changedSep 5, 2026

changedInput schema / properties / address / description

Previous value: -"A bare node id, 'node-id#section-slug', or 'decision:<decision-id>'."New value: +"A bare node id; 'node-id#section-slug', the slug read off a Node's sections, a Card claim's sources, or a Link's occurrence (slugs are not guessable); or 'decision:<decision-id>'."

Changed1 schema field changedSep 2, 2026
- changedOutput schema / properties / projection / const
```
Previous value: -"agent-projection/v4"New value: +"agent-projection/v5"
```
Changed1 schema field changedAug 26, 2026
- changedOutput schema / properties / projection / const
```
Previous value: -"agent-projection/v3"New value: +"agent-projection/v4"
```

Changed1 schema field changedAug 26, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "coherence": {
+      "type": "string"
+    },
+    "data": {
+      "type": "object"
+    },
+    "payload_class": {
+      "enum": [
+        "section",
+        "node",
+        "decision"
+      ],
+      "type": "string"
+    },
+    "projection": {
+      "const": "agent-projection/v3"
+    },
+    "scope": {
+      "type": "object"
+    }
+  },
+  "required": [
+    "projection",
+    "coherence",
+    "payload_class",
+    "scope",
+    "data"
+  ],
+  "type": "object"
+}

Changed2 schema fields changedAug 25, 2026

changedInput schema / properties / address / description

Previous value: -"One canonical address: a bare node id for the complete Node, 'node-id#section-slug' for one Section, or 'decision:<decision-id>' for one Decision record."New value: +"A bare node id, 'node-id#section-slug', or 'decision:<decision-id>'."

changedInput schema / properties / expected_revision / description

Previous value: -"Optional coherence marker: the Release version (for example 'v1.0.2') read off any previous payload's 'coherence' field. Omit on a first call. When carried, a promotion that has moved the active Release off this marker is refused with the 'revision_changed' error rather than silently answered from a different Release."New value: +"A prior payload's 'coherence'; 'revision_changed' refuses a moved Release."

Changed2 schema fields changedAug 24, 2026

addedInput schema / properties / address / description

Added value: +"One canonical address: a bare node id for the complete Node, 'node-id#section-slug' for one Section, or 'decision:<decision-id>' for one Decision record."

addedInput schema / properties / expected_revision / description

Added value: +"Optional coherence marker: the Release version (for example 'v1.0.2') read off any previous payload's 'coherence' field. Omit on a first call. When carried, a promotion that has moved the active Release off this marker is refused with the 'revision_changed' error rather than silently answered from a different Release."

First observedAug 24, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the readOnly/idempotent annotations, it discloses scope ('relationship occurrences are omitted'), error semantics ('invalid_argument', wrong-slug refusal lists real slugs), and revision-pinning refusal ('revision_changed'). That is exactly the extra behavioral context annotations cannot carry.

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

Conciseness5/5

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

Four dense sentences with no filler; resolution behavior is front-loaded before the usage trigger and error cases. Every sentence carries distinct information.

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?

An output schema exists, yet the description still sets expectations about what each address form returns, and it covers both error paths. Nothing an agent needs in order to call this correctly is missing.

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%, so the baseline is 3, but the description ties the 'address' parameter to concrete return shapes: bare Node id yields identity/tree position/Hook/every Section, while section/decision/term addresses yield one item. That adds meaning the schema's format list alone does not convey.

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+resource ('Read the full text at one exact Atlas address') and then disambiguates the four address forms, explaining what each resolves to. An agent can tell this is the exact-read tool versus the summary/navigation siblings without opening the schema.

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?

'Use when a summary is not enough or you need exact wording to cite' gives an explicit trigger condition. It implicitly positions this against atlas_navigate/atlas_orient (which supply summaries) but never names an alternative or states a hard when-not, so it stops short of a 5.

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

All Agentic Atlas tools Inspect

Try in Browser

Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?