Skip to main content
Glama

Agentic Atlas

by dev.agentic-atlas
OverviewDiscussionsAdmin

Read Atlas Links

atlas_links
Read-onlyIdempotent

Page one subject's relationship occurrences, outbound then inbound, each with direction, reference class, source Section, and the far end's Hook, plus its identity unless the class is 'undisclosed'.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
boundNoOccurrences per page, 1-50.
cursorNoscope.next_cursor from a prior atlas_links page; repeat the same other arguments.
subjectYesThe node id whose occurrences are paged.
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": [
+        "links"
+      ],
+      "type": "string"
+    },
+    "projection": {
+      "const": "agent-projection/v3"
+    },
+    "scope": {
+      "type": "object"
+    }
+  },
+  "required": [
+    "projection",
+    "coherence",
+    "payload_class",
+    "scope",
+    "data"
+  ],
+  "type": "object"
+}
  5. Changed4 schema fields changed
    • changedInput schema / properties / bound / description
      Previous value: -"Maximum occurrences per page, 1-50 (default 12)."New value: +"Occurrences per page, 1-50."
    • changedInput schema / properties / cursor / description
      Previous value: -"Opaque continuation token from a previous atlas_links payload's 'scope.next_cursor'. Repeat the same arguments alongside it; a cursor minted for a different request or a different Release is refused with 'invalid_argument'."New value: +"scope.next_cursor from a prior atlas_links page; repeat the same other arguments."
    • 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 / subject / description
      Previous value: -"The one canonical node id whose relationship occurrences are paged."New value: +"The node id whose occurrences are paged."
  6. Changed4 schema fields changed
    • addedInput schema / properties / bound / description
      Added value: +"Maximum occurrences per page, 1-50 (default 12)."
    • addedInput schema / properties / cursor / description
      Added value: +"Opaque continuation token from a previous atlas_links payload's 'scope.next_cursor'. Repeat the same arguments alongside it; a cursor minted for a different request or a different Release is refused with 'invalid_argument'."
    • 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 / subject / description
      Added value: +"The one canonical node id whose relationship occurrences are paged."
  7. First observed

TDQS

A4/5.0
Behavior4/5

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

The description adds meaningful behavioral details beyond the annotations: it specifies the ordering (outbound then inbound), the inclusion of identity unless the class is 'undisclosed', and that it returns direction, reference class, source Section, and far end's Hook. Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the description complements rather than repeats. It does not mention the revision check, but that is covered in the expected_revision parameter description.

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 a single, dense sentence that front-loads the primary action ('Page one subject's relationship occurrences') and then efficiently lists the specific details. There is no redundant phrasing or filler. It is concise yet packed with the key information needed to understand the tool's behavior.

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?

Given that an output schema is present, the description does not need to explain the return format. It covers the essential behavioral aspects: what is returned (direction, reference class, source Section, far end's Hook, identity condition), the ordering, and pagination via 'Page'. The revision handling is documented in the expected_revision parameter, and the annotations cover safety. A minor omission is the lack of mention of the revision check, but that is already in the schema, so the description is sufficiently complete for correct invocation.

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?

The input schema provides 100% coverage with descriptions for all four parameters, so the baseline is 3. The description does not add additional meaning to the parameters themselves; it focuses on the output content rather than parameter usage. For instance, 'subject' is described in the schema as 'The node id whose occurrences are paged,' which aligns with the description's 'one subject'. No extra value is added beyond 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?

The description states a specific action: 'Page one subject's relationship occurrences', and details the output fields and ordering. It clearly differentiates from siblings by focusing on relationship occurrences, while other tools like atlas_navigate or atlas_read likely handle different concerns. The verb 'Page' and the resource are explicit, making the purpose unmistakable.

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 does not explicitly state when to use this tool versus its siblings. It implies that it is for listing relationship occurrences, but there is no direct guidance on when to prefer it over atlas_navigate, atlas_read, etc. The usage context is inferred from the tool's name and description, not explicitly given.

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