Agentic Atlas

Read an Atlas Node or Section

atlas_read

Read-onlyIdempotent

Read a complete Node (bare id: identity, hierarchy, Hook, and every Section; relationship occurrences are omitted), one Section ('node-id#section-slug'), one Decision record ('decision:'), or one exact glossary definition ('term:').

Input Schema

TableJSON Schema

Name	Required	Description	Default
`address`	Yes	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>'.
`expected_revision`	No	A prior payload's 'coherence'; 'revision_changed' refuses a moved Release.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	Yes
`scope`	Yes
`coherence`	Yes
`projection`	Yes
`payload_class`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

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.5/5.0

Behavior4/5

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

Annotations already carry readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the description need not repeat those. It adds valuable behavioral context by defining what a 'complete Node' includes and explicitly stating that relationship occurrences are omitted. The 'slugs are not guessable' warning also helps call construction. No contradiction with annotations.

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?

A single well-structured sentence front-loads the action and resource scope, then uses semicolon-separated address patterns for clarity. Every clause earns its place, and there is no filler or restatement of the title.

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?

Given a 2-parameter schema with 100% coverage, an output schema, and safety annotations, the description fully covers the operational contract: what can be read, what each address form means, and what is omitted. Nothing critical an agent needs to invoke it 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 description coverage is 100%, so the address parameter is already well documented. The description adds meaning beyond the schema by clarifying that a bare id returns a complete Node with identity/hierarchy/Hook/Sections and by framing each address form as a distinct read target. This exceeds the baseline 3 without duplicating 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 'Read' and enumerates the exact resource types: complete Node (identity, hierarchy, Hook, Sections, excluding relationship occurrences), Section, Decision record, and glossary definition. This level of specificity clearly differentiates it from sibling tools without requiring schema inspection.

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?

Provides clear context for when to use this tool: whenever a Node, Section, Decision record, or glossary definition is needed. It also notes that relationship occurrences are omitted, which implicitly tells the agent to look elsewhere, likely atlas_links, if relationship data is required. It does not name alternatives explicitly, 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

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?