Skip to main content
Glama

Agentic Atlas

by dev.agentic-atlas
OverviewDiscussionsAdmin

Read Atlas Cards

atlas_cards
Read-onlyIdempotent

Read 1-8 canonical ids as one ordered Card per id: identity, Hook, and sealed claims with source addresses. Set provenance=true to expand every cited source's Release-bound audit facts in the same atomic response.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idsYes1-8 distinct canonical node ids.
provenanceNoInclude expanded audit facts for cited sources.
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
    • changedInput schema / properties / ids / description
      Previous value: -"1-4 distinct canonical node ids."New value: +"1-8 distinct canonical node ids."
  2. Changed2 schema fields changed
    • addedInput schema / properties / provenance
      Added value: +{
+  "default": false,
+  "description": "Include expanded audit facts for cited sources.",
+  "type": "boolean"
+}
    • changedOutput schema / properties / projection / const
      Previous value: -"agent-projection/v5"New value: +"agent-projection/v6"
  3. Changed1 schema field changed
    • changedOutput schema / properties / projection / const
      Previous value: -"agent-projection/v4"New value: +"agent-projection/v5"
  4. Changed1 schema field changed
    • changedOutput schema / properties / projection / const
      Previous value: -"agent-projection/v3"New value: +"agent-projection/v4"
  5. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "coherence": {
+      "type": "string"
+    },
+    "data": {
+      "type": "object"
+    },
+    "payload_class": {
+      "enum": [
+        "cards"
+      ],
+      "type": "string"
+    },
+    "projection": {
+      "const": "agent-projection/v3"
+    },
+    "scope": {
+      "type": "object"
+    }
+  },
+  "required": [
+    "projection",
+    "coherence",
+    "payload_class",
+    "scope",
+    "data"
+  ],
+  "type": "object"
+}
  6. 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 / ids / description
      Previous value: -"1 to 4 distinct canonical node ids, for example taken from atlas_orient candidates, atlas_links targets, or atlas_navigate tree entries."New value: +"1-4 distinct canonical node ids."
  7. 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 / ids / description
      Added value: +"1 to 4 distinct canonical node ids, for example taken from atlas_orient candidates, atlas_links targets, or atlas_navigate tree entries."
  8. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds useful behavior beyond that: the 1-8 id bound, ordered Card output, atomic response semantics, and the fact that provenance=true expands every cited source's audit facts in the same response.

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?

Two sentences with the core action front-loaded and no filler. The second sentence efficiently covers the provenance flag, though the domain vocabulary is dense and could obscure the core read operation for an unfamiliar agent.

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

Completeness3/5

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

Given annotations covering safety, a 100%-covered input schema, and an output schema, the description is mostly complete for invocation. However, it omits sibling differentiation and when-to-use guidance, which are material for an agent choosing among the five atlas tools.

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 already documents ids, provenance, and expected_revision. The description adds marginal context by mapping ids to ordered Cards and clarifying that provenance expansion occurs atomically, but it does not add syntax or format details beyond what the schema provides.

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 states a specific verb and resource: reading 1-8 canonical ids as one ordered Card per id, with fields (identity, Hook, sealed claims, source addresses). It is clear what the tool does, but it does not distinguish itself from siblings such as atlas_read, atlas_links, or atlas_navigate.

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

Usage Guidelines2/5

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

There is no guidance on when to use atlas_cards versus the sibling tools (atlas_read, atlas_links, atlas_navigate, atlas_orient). The only usage cue is the implicit 1-8 id limit, which is operational rather than comparative.

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