Skip to main content
Glama

Agentic Atlas

by dev.agentic-atlas
OverviewDiscussionsAdmin

Get Atlas Summary Cards by ID

atlas_cards
Read-onlyIdempotent

Get one summary Card per Atlas Node id: its Hook (one-line summary) and the publisher's claims (thesis, law, when-to-reach, or claim), each citing its source Sections. Use when you hold ids and want their guidance without full text, such as to compare entries. Cards return in request order. Atomic: one unknown or Roadmap-only (unpublished) id refuses the whole batch as batch_not_atomic, naming the rejected ids.

Input Schema

NameRequiredDescriptionDefault
idsYesThe Nodes to summarize, as bare ids (no '#section') such as atlas_orient candidate ids or atlas_navigate tree ids; Cards return in this order.
provenanceNotrue also returns each cited source's content digest and publisher attestation (who, when), plus the Release's digests: a larger response.
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
dataYescards, one per requested id in request order: id, title, kind, hook, and claims (id, text, field, sources as 'node-id#section-slug'). With provenance=true, also provenance: release (version and digests) and addresses, each with address, dependency_digest, distillation, and attestation (publisher, attested_on).
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: -"cards, one per requested id in request order: id, title, kind, status, hook, and claims (id, text, field, sources as 'node-id#section-slug'). With provenance=true, also provenance: release (version and digests) and addresses, each with address, dependency_digest, distillation, and attestation (publisher, attested_on)."New value: +"cards, one per requested id in request order: id, title, kind, hook, and claims (id, text, field, sources as 'node-id#section-slug'). With provenance=true, also provenance: release (version and digests) and addresses, each with address, dependency_digest, distillation, and attestation (publisher, attested_on)."
    • removedOutput schema / properties / payload_class
      Removed value: -{
-  "enum": [
-    "cards"
-  ],
-  "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 / ids / description
      Previous value: -"1-8 distinct bare Node ids (no '#section'), e.g. atlas_orient candidate ids or atlas_navigate tree ids; Cards return in this order."New value: +"The Nodes to summarize, as bare ids (no '#section') such as atlas_orient candidate ids or atlas_navigate tree ids; Cards return in this order."
  4. Changed7 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 / ids / description
      Previous value: -"The subjects to read, 1-8 distinct bare canonical node ids, e.g. atlas_orient candidate ids or atlas_navigate tree ids; Cards return in this order."New value: +"1-8 distinct bare Node ids (no '#section'), e.g. atlas_orient candidate ids or atlas_navigate tree ids; Cards return in this order."
    • addedInput schema / properties / ids / maxItems
      Added value: +8
    • addedInput schema / properties / ids / minItems
      Added value: +1
    • addedInput schema / properties / ids / uniqueItems
      Added value: +true
    • changedInput schema / properties / provenance / description
      Previous value: -"Include expanded audit facts for cited sources."New value: +"true also returns each cited source's content digest and publisher attestation (who, when), plus the Release's digests: a larger response."
  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 / ids / description
      Previous value: -"1-8 distinct canonical node ids."New value: +"The subjects to read, 1-8 distinct bare canonical node ids, e.g. atlas_orient candidate ids or atlas_navigate tree ids; Cards return in this order."
    • addedOutput schema / properties / data / description
      Added value: +"cards, one per requested id in request order: id, title, kind, status, hook, and claims (id, text, field, sources as 'node-id#section-slug'). With provenance=true, also provenance: release (version and digests) and addresses, each with address, dependency_digest, distillation, and attestation (publisher, attested_on)."
  6. 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."
  7. 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"
  8. Changed1 schema field changed
    • changedOutput schema / properties / projection / const
      Previous value: -"agent-projection/v4"New value: +"agent-projection/v5"
  9. Changed1 schema field changed
    • changedOutput schema / properties / projection / const
      Previous value: -"agent-projection/v3"New value: +"agent-projection/v4"
  10. 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"
+}
  11. 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."
  12. 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."
  13. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world; the description adds real behavioral context beyond them: strict atomicity (one unknown or Roadmap-only id fails the whole batch as batch_not_atomic, naming rejected ids), request-order output, and revision pinning consequences. These are exactly the failure modes an agent needs to anticipate.

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-loads what a Card is, then when to use it, then the atomicity caveat — a logical order with no filler. The dense, jargon-heavy phrasing ("Roadmap-only", "batch_not_atomic", "coherence") costs a little readability.

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?

With an output schema present, return values need no further explanation, yet the description still covers card contents, ordering, provenance opt-in, revision pinning and batch failure semantics. Nothing needed to invoke the tool 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 structured fields already carry most param meaning. The description still adds value beyond the schema by defining validity failure modes for ids (unknown vs Roadmap-only) and the atomic-batch consequence, though it adds little on provenance/expected_revision beyond what the schema says.

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 (get summary Cards per Atlas Node id) and enumerates what a Card contains — Hook and publisher claims (thesis, law, when-to-reach, claim) with source Sections. This contrasts implicitly but clearly with atlas_read's full text, so an agent can distinguish the retrieval modes.

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 you hold ids and want their guidance without full text, such as to compare entries" gives a concrete usage condition, and it names where ids come from (atlas_orient, atlas_navigate). It stops short of naming the alternative tool explicitly, so the routing to atlas_read must be inferred.

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
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources