Skip to main content
Glama

Agentic Atlas

by dev.agentic-atlas
OverviewDiscussionsAdmin

Navigate the Atlas

atlas_navigate
Read-onlyIdempotent

Read 'tree', the canonical ordered traversal of every published node, or 'tour', the publisher-curated first learning path.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
viewNo'tree' for the canonical traversal, 'tour' for the curated walk.tree
expected_revisionNoA prior payload's 'coherence'; 'revision_changed' refuses a moved Release.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYes
scopeYes
coherenceYes
projectionYes
payload_classYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / properties / projection / const
      Previous value: -"agent-projection/v5"New value: +"agent-projection/v6"
  2. Changed1 schema field changed
    • changedOutput schema / properties / projection / const
      Previous value: -"agent-projection/v4"New value: +"agent-projection/v5"
  3. Changed1 schema field changed
    • changedOutput schema / properties / projection / const
      Previous value: -"agent-projection/v3"New value: +"agent-projection/v4"
  4. 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"
+}
  5. 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."
  6. 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."
  7. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already establish readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is clear. The description adds useful semantic context about scope ('every published node') and curation, but it does not disclose behavior around expected_revision or error/refusal cases, which are only partially visible in the schema.

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?

The description is one efficient, front-loaded sentence. Every clause earns its place by defining both views without repetition or filler.

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

Completeness4/5

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

For a read-only, idempotent tool with two optional parameters and an output schema, the description is nearly complete. It explains the two views, while the schema covers parameter details and the annotations cover safety behavior. A little more explicit sibling differentiation would make it fully complete.

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 the schema fully documents both parameters. The description repeats the tree/tour meaning already present in the schema and adds no additional parameter semantics beyond that, so the baseline of 3 is appropriate.

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

Purpose4/5

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

The description uses a specific verb ('Read') and clearly names two concrete resources: 'tree' (the canonical ordered traversal of every published node) and 'tour' (the publisher-curated first learning path). It is clear what the tool does, though it does not explicitly distinguish itself from sibling tools like atlas_read.

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

Usage Guidelines3/5

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

The description implies the use cases by defining tree and tour: tree for the full canonical order, tour for a curated path. However, it does not explicitly state when to use this tool over siblings or when to avoid it, leaving some routing to inference.

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