Skip to main content
Glama

Agentic Atlas

by dev.agentic-atlas
OverviewDiscussionsAdmin

Browse the Atlas Tree or Guided Tour

atlas_navigate
Read-onlyIdempotent

Browse the whole Atlas in the publisher's order: the canonical tree of every published Node, or the guided first learning path, an introduction then steps each naming a Node id with narration. Use to survey what exists or to start learning with no topic in mind. Neither view carries entry text or claims; the tour is null if none is published.

Input Schema

NameRequiredDescriptionDefault
viewNoChoose tree to survey every published Node in canonical order, or tour to follow the publisher's guided first learning path.tree
expected_revisionNoPins 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

NameRequiredDescriptionDefault
dataYestree: tree entries (id, title, depth). tour: path (id, title, intro, steps of node id, narration), or null when the Release seals no tour.
scopeYes
coherenceYes
projectionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / properties / projection / const
      Previous value: -"agent-projection/v7"New value: +"agent-projection/v8"
  2. Changed4 schema fields changed
    • changedOutput schema / properties / data / description
      Previous value: -"tree: tree entries (id, title, position, depth). tour: path (id, title, intro, steps of position, node id, narration), or null when the Release seals no tour."New value: +"tree: tree entries (id, title, depth). tour: path (id, title, intro, steps of node id, narration), or null when the Release seals no tour."
    • removedOutput schema / properties / payload_class
      Removed value: -{
-  "enum": [
-    "tree",
-    "tour"
-  ],
-  "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"
+]
  3. Changed1 schema field changed
    • changedInput schema / properties / view / description
      Previous value: -"'tree': every published Node in canonical order; 'tour': the publisher's guided first learning path."New value: +"Choose tree to survey every published Node in canonical order, or tour to follow the publisher's guided first learning path."
  4. Changed3 schema fields changed
    • 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."
    • changedInput schema / properties / view / description
      Previous value: -"Which ordering to read: 'tree' lists every published node in canonical order; 'tour' walks the publisher-curated first learning path."New value: +"'tree': every published Node in canonical order; 'tour': the publisher's guided first learning path."
  5. Changed3 schema fields changed
    • 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."
    • changedInput schema / properties / view / description
      Previous value: -"'tree' for the canonical traversal, 'tour' for the curated walk."New value: +"Which ordering to read: 'tree' lists every published node in canonical order; 'tour' walks the publisher-curated first learning path."
    • addedOutput schema / properties / data / description
      Added value: +"tree: tree entries (id, title, position, depth). tour: path (id, title, intro, steps of position, node id, narration), or null when the Release seals no tour."
  6. Changed1 schema field changed
    • changedOutput schema / properties / projection / const
      Previous value: -"agent-projection/v5"New value: +"agent-projection/v6"
  7. Changed1 schema field changed
    • changedOutput schema / properties / projection / const
      Previous value: -"agent-projection/v4"New value: +"agent-projection/v5"
  8. Changed1 schema field changed
    • changedOutput schema / properties / projection / const
      Previous value: -"agent-projection/v3"New value: +"agent-projection/v4"
  9. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "coherence": {
+      "type": "string"
+    },
+    "data": {
+      "type": "object"
+    },
+    "payload_class": {
+      "enum": [
+        "tree",
+        "tour"
+      ],
+      "type": "string"
+    },
+    "projection": {
+      "const": "agent-projection/v3"
+    },
+    "scope": {
+      "type": "object"
+    }
+  },
+  "required": [
+    "projection",
+    "coherence",
+    "payload_class",
+    "scope",
+    "data"
+  ],
+  "type": "object"
+}
  10. Changed2 schema fields changed
    • 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."
    • changedInput schema / properties / view / description
      Previous value: -"'tree' for the canonical ordered traversal of every published node; 'tour' for the publisher-curated first learning path."New value: +"'tree' for the canonical traversal, 'tour' for the curated walk."
  11. Changed2 schema fields changed
    • 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."
    • addedInput schema / properties / view / description
      Added value: +"'tree' for the canonical ordered traversal of every published node; 'tour' for the publisher-curated first learning path."
  12. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so they carry the burden. The description still adds real value beyond them: the content boundary ('neither view carries entry text or claims') and the null-tour edge case, which an agent cannot infer 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 primary purpose, then the usage trigger, then the return caveat; no sentence is wasted. The opening sentence is long and appositive-heavy, which slightly blunts scannability, but it is proportionate to the two-mode tool.

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?

For a two-parameter, default-valued, read-only browse tool with full annotation coverage and an output schema, nothing needed to invoke it correctly is missing. The description even covers the one edge case (unpublished tour) that the structured fields leave open.

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

Parameters3/5

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

Schema description coverage is 100%, so both parameters are already documented, including the enum values and the expected_revision rejection behavior ('revision_changed'). The description reinforces tree ordering and the tour null case but adds no syntax or meaning beyond the schema, matching the baseline.

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?

The description names a concrete verb (browse) and resource (the Atlas), then enumerates the two modes precisely: the canonical tree of every published Node, or the guided first learning path. The clause 'Neither view carries entry text or claims' implicitly separates it from atlas_read, so an agent can tell what this tool is not without opening a 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 to survey what exists or to start learning with no topic in mind' gives a clear use condition plus an implicit exclusion (topic-driven lookups belong elsewhere). It stops short of naming a specific sibling alternative, so it is clear context rather than explicit when/when-not routing.

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

All Agentic Atlas toolsInspect
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