Skip to main content
Glama

Search Atlas Nodes, Decisions, and Terms

atlas_orient
Read-onlyIdempotent

Find Atlas entries by topic when you hold no id; an id you already hold can be read directly. Searches Nodes (patterns, concepts, examples) and Roadmap entries (announced, unpublished); kind narrows it to one Node kind, Decisions, or glossary terms. Node discovery preserves leading lexical matches and adds related entries with task vocabulary, using references in either direction. Related candidates explain their connection; direct matches have no via. Empty listings and exact id/title lookups stay lexical. Returns ranked ids with Hooks (one-line summaries; a term's is its whole definition), paged with a cursor. A miss is an empty page; invalid arguments are refused as invalid_argument.

Input Schema

NameRequiredDescriptionDefault
kindNoNarrows the search to one Node kind, to Decision records, or to glossary terms. Omit it to search every Node kind plus Roadmap entries (announced, unpublished); setting it leaves Roadmap entries out.
boundNoHow many ranked candidates this call returns; raise it to compare more matches at once, and continue past it with cursor.
queryNoA topic or question in ordinary design vocabulary. Lexical matches use canonical ids, titles, Hooks, claims, then Section headings and bodies, with rarer words weighing more; a word of four or more characters also matches longer tokens it begins. Section text supplies direct candidates only when no subject matches an identity field. Node discovery also includes neighbors matching query terms through references in either direction; via explains the connection, and total counts the candidates. kind='decision' searches Decision ids, titles, and bodies; kind='term', keys and definitions. Empty lists every subject of the kind.
cursorNoscope.next_cursor from a prior atlas_orient page; repeat the same other arguments.
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
dataYescandidates, ranked. A Node candidate has id, hook, and disclosure ('full', or 'roadmap' with its title); a Decision or term candidate has id, which is its atlas_read address, and hook. A related Node also has via: seed id, reference direction relative to that seed, and the source Section address.
scopeYes
coherenceYes
projectionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / bound / default
      Previous value: -3New value: +8
    • changedInput schema / properties / query / description
      Previous value: -"A topic or question in ordinary design vocabulary. Words match whole words (four or more characters also match longer words they begin; stopwords drop) in canonical ids, titles, Hooks, and claims, then Section headings and bodies; rarer words weigh more. Section text makes a candidate only when no subject matches elsewhere, so total counts the candidates. kind='decision' searches Decision ids, titles, and bodies; kind='term', keys and definitions. Empty lists every subject of the kind."New value: +"A topic or question in ordinary design vocabulary. Lexical matches use canonical ids, titles, Hooks, claims, then Section headings and bodies, with rarer words weighing more; a word of four or more characters also matches longer tokens it begins. Section text supplies direct candidates only when no subject matches an identity field. Node discovery also includes neighbors matching query terms through references in either direction; via explains the connection, and total counts the candidates. kind='decision' searches Decision ids, titles, and bodies; kind='term', keys and definitions. Empty lists every subject of the kind."
    • changedOutput schema / properties / data / description
      Previous value: -"candidates, ranked. A Node candidate has id, hook, and disclosure ('full', or 'roadmap' with its title); a Decision or term candidate has id, which is its atlas_read address, and hook."New value: +"candidates, ranked. A Node candidate has id, hook, and disclosure ('full', or 'roadmap' with its title); a Decision or term candidate has id, which is its atlas_read address, and hook. A related Node also has via: seed id, reference direction relative to that seed, and the source Section address."
    • changedOutput schema / properties / projection / const
      Previous value: -"agent-projection/v7"New value: +"agent-projection/v8"
  2. Changed5 schema fields changed
    • removedInput schema / properties / status
      Removed value: -{
      -  "anyOf": [
      -    {
      -      "enum": [
      -        "seeded",
      -        "drafting",
      -        "fleshed",
      -        "needs-work",
      -        "stable"
      -      ],
      -      "type": "string"
      -    },
      -    {
      -      "type": "null"
      -    }
      -  ],
      -  "default": null,
      -  "description": "Maturity filter. Published Nodes are 'fleshed' or 'stable'; Roadmap entries may be any rung. Refused with kind 'decision' or 'term'."
      -}
    • changedOutput schema / properties / data / description
      Previous value: -"candidates, ranked. A Node candidate has id, status, hook, and disclosure ('full', or 'roadmap' with its title); a Decision or term candidate has id, which is its atlas_read address, and hook."New value: +"candidates, ranked. A Node candidate has id, hook, and disclosure ('full', or 'roadmap' with its title); a Decision or term candidate has id, which is its atlas_read address, and hook."
    • removedOutput schema / properties / payload_class
      Removed value: -{
      -  "enum": [
      -    "orient"
      -  ],
      -  "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. Changed2 schema fields changed
    • changedInput schema / properties / bound / description
      Previous value: -"Candidates per page; the rest continue through cursor."New value: +"How many ranked candidates this call returns; raise it to compare more matches at once, and continue past it with cursor."
    • changedInput schema / properties / kind / description
      Previous value: -"Which subjects to search: 'pattern', 'concept', or 'example' Nodes, 'decision' records, or glossary 'term's. Omit for every Node kind plus Roadmap entries, which any kind excludes."New value: +"Narrows the search to one Node kind, to Decision records, or to glossary terms. Omit it to search every Node kind plus Roadmap entries (announced, unpublished); setting it leaves Roadmap entries out."
  4. Changed11 schema fields changed
    • changedInput schema / properties / bound / description
      Previous value: -"How many candidates one page returns, 1-8; the rest continue through cursor."New value: +"Candidates per page; the rest continue through cursor."
    • addedInput schema / properties / bound / maximum
      Added value: +8
    • addedInput schema / properties / bound / minimum
      Added value: +1
    • 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 / kind / anyOf
      Previous value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "enum": [
      +      "concept",
      +      "pattern",
      +      "example",
      +      "decision",
      +      "term"
      +    ],
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / kind / description
      Previous value: -"Which subjects to search: 'pattern', 'concept', or 'example' Nodes, 'decision' records, or glossary 'term's. Omit to search published Nodes of every kind plus Roadmap entries; any kind excludes Roadmap entries. Decision and term candidates carry directly readable addresses."New value: +"Which subjects to search: 'pattern', 'concept', or 'example' Nodes, 'decision' records, or glossary 'term's. Omit for every Node kind plus Roadmap entries, which any kind excludes."
    • changedInput schema / properties / query / anyOf
      Previous value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "examples": [
      +      "keep bulky context out of the window"
      +    ],
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / query / description
      Previous value: -"Ordinary design vocabulary. Stopwords are dropped and each remaining word matches whole tokens (a word of four or more characters also matches longer tokens it begins) in canonical ids, titles, Hooks, sealed Card claims, and published Section headings and bodies, each word weighed by how few subjects carry it in an identity field. A Section match orders a candidate but makes one only when no subject matches in an identity field, so total counts the candidates, not every subject a word touches. With kind='decision', the searchable identity is the raw canonical id, title, and complete sealed Decision body. With kind='term', the canonical glossary key and sealed definition are searched. Empty lists every subject of the selected kind."New value: +"A topic or question in ordinary design vocabulary. Words match whole words (four or more characters also match longer words they begin; stopwords drop) in canonical ids, titles, Hooks, and claims, then Section headings and bodies; rarer words weigh more. Section text makes a candidate only when no subject matches elsewhere, so total counts the candidates. kind='decision' searches Decision ids, titles, and bodies; kind='term', keys and definitions. Empty lists every subject of the kind."
    • changedInput schema / properties / status / anyOf
      Previous value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "enum": [
      +      "seeded",
      +      "drafting",
      +      "fleshed",
      +      "needs-work",
      +      "stable"
      +    ],
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / status / description
      Previous value: -"One status-ladder rung; published subjects are 'fleshed' or 'stable'."New value: +"Maturity filter. Published Nodes are 'fleshed' or 'stable'; Roadmap entries may be any rung. Refused with kind 'decision' or 'term'."
  5. Changed4 schema fields changed
    • changedInput schema / properties / bound / description
      Previous value: -"Candidates per page, 1-8."New value: +"How many candidates one page returns, 1-8; the rest continue through cursor."
    • 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 / kind / description
      Previous value: -"Restrict to 'pattern', 'concept', 'example', or 'decision', or 'term'; any kind excludes Roadmap entries. Decision and term candidates carry directly readable addresses."New value: +"Which subjects to search: 'pattern', 'concept', or 'example' Nodes, 'decision' records, or glossary 'term's. Omit to search published Nodes of every kind plus Roadmap entries; any kind excludes Roadmap entries. Decision and term candidates carry directly readable addresses."
    • addedOutput schema / properties / data / description
      Added value: +"candidates, ranked. A Node candidate has id, status, hook, and disclosure ('full', or 'roadmap' with its title); a Decision or term candidate has id, which is its atlas_read address, and hook."
  6. Changed4 schema fields changed
    • addedInput schema / properties / query / anyOf
      Added value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • addedInput schema / properties / query / default
      Added value: +null
    • removedInput schema / properties / query / type
      Removed value: -"string"
    • removedInput schema / required
      Removed value: -[
      -  "query"
      -]
  7. Changed3 schema fields changed
    • changedInput schema / properties / kind / description
      Previous value: -"Restrict to 'pattern', 'concept', or 'example'; excludes Roadmap entries."New value: +"Restrict to 'pattern', 'concept', 'example', or 'decision', or 'term'; any kind excludes Roadmap entries. Decision and term candidates carry directly readable addresses."
    • changedInput schema / properties / query / description
      Previous value: -"Ordinary design vocabulary. Stopwords are dropped and each remaining word matches whole tokens (a word of four or more characters also matches longer tokens it begins) in canonical ids, titles, Hooks, sealed Card claims, and published Section headings and bodies, each word weighed by how few subjects carry it in an identity field. A Section match orders a candidate but makes one only when no subject matches in an identity field, so total counts the candidates, not every subject a word touches. Empty lists every subject."New value: +"Ordinary design vocabulary. Stopwords are dropped and each remaining word matches whole tokens (a word of four or more characters also matches longer tokens it begins) in canonical ids, titles, Hooks, sealed Card claims, and published Section headings and bodies, each word weighed by how few subjects carry it in an identity field. A Section match orders a candidate but makes one only when no subject matches in an identity field, so total counts the candidates, not every subject a word touches. With kind='decision', the searchable identity is the raw canonical id, title, and complete sealed Decision body. With kind='term', the canonical glossary key and sealed definition are searched. Empty lists every subject of the selected kind."
    • changedOutput schema / properties / projection / const
      Previous value: -"agent-projection/v5"New value: +"agent-projection/v6"
  8. Changed1 schema field changed
    • changedInput schema / properties / query / description
      Previous value: -"Ordinary design vocabulary. Stopwords are dropped and each remaining word matches whole tokens (a word of four or more characters also matches longer tokens it begins) in canonical ids, titles, Hooks, sealed Card claims, and published Section headings and bodies; Section text is searched only when no subject matches in an identity field, and total counts subjects with at least one matching term. Empty lists every subject."New value: +"Ordinary design vocabulary. Stopwords are dropped and each remaining word matches whole tokens (a word of four or more characters also matches longer tokens it begins) in canonical ids, titles, Hooks, sealed Card claims, and published Section headings and bodies, each word weighed by how few subjects carry it in an identity field. A Section match orders a candidate but makes one only when no subject matches in an identity field, so total counts the candidates, not every subject a word touches. Empty lists every subject."
  9. Changed2 schema fields changed
    • changedInput schema / properties / query / description
      Previous value: -"Ordinary design vocabulary, matched case-insensitively against canonical ids, titles, Hooks, and published Section headings and bodies; empty lists every subject."New value: +"Ordinary design vocabulary. Stopwords are dropped and each remaining word matches whole tokens (a word of four or more characters also matches longer tokens it begins) in canonical ids, titles, Hooks, sealed Card claims, and published Section headings and bodies; Section text is searched only when no subject matches in an identity field, and total counts subjects with at least one matching term. Empty lists every subject."
    • changedOutput schema / properties / projection / const
      Previous value: -"agent-projection/v4"New value: +"agent-projection/v5"
  10. Changed1 schema field changed
    • changedOutput schema / properties / projection / const
      Previous value: -"agent-projection/v3"New value: +"agent-projection/v4"
  11. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "coherence": {
      +      "type": "string"
      +    },
      +    "data": {
      +      "type": "object"
      +    },
      +    "payload_class": {
      +      "enum": [
      +        "orient"
      +      ],
      +      "type": "string"
      +    },
      +    "projection": {
      +      "const": "agent-projection/v3"
      +    },
      +    "scope": {
      +      "type": "object"
      +    }
      +  },
      +  "required": [
      +    "projection",
      +    "coherence",
      +    "payload_class",
      +    "scope",
      +    "data"
      +  ],
      +  "type": "object"
      +}
  12. Changed6 schema fields changed
    • changedInput schema / properties / bound / description
      Previous value: -"Maximum candidates per page, 1-8 (default 3)."New value: +"Candidates per page, 1-8."
    • changedInput schema / properties / cursor / description
      Previous value: -"Opaque continuation token from a previous atlas_orient 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_orient 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 / kind / description
      Previous value: -"Restrict candidates to one node kind: 'pattern', 'concept', or 'example'. Roadmap entries carry no kind, so any kind filter excludes them."New value: +"Restrict to 'pattern', 'concept', or 'example'; excludes Roadmap entries."
    • changedInput schema / properties / query / description
      Previous value: -"Ordinary design vocabulary naming the problem or subject (for example 'context window budget'). Terms are split on non-alphanumeric characters and matched case-insensitively against canonical ids, titles, Hooks, and published Section headings and bodies. Section text is searched only when those identity fields produce no candidates, and a body-only match requires every query term. An empty string lists every subject in manifest order."New value: +"Ordinary design vocabulary, matched case-insensitively against canonical ids, titles, Hooks, and published Section headings and bodies; empty lists every subject."
    • changedInput schema / properties / status / description
      Previous value: -"Restrict candidates to one maturity rung of the corpus status ladder; published subjects sit at 'fleshed' or 'stable'."New value: +"One status-ladder rung; published subjects are 'fleshed' or 'stable'."
  13. Changed1 schema field changed
    • changedInput schema / properties / query / description
      Previous value: -"Ordinary design vocabulary naming the problem or subject (for example 'context window budget'). Terms are split on non-alphanumeric characters and matched case-insensitively; an empty string lists every subject in manifest order."New value: +"Ordinary design vocabulary naming the problem or subject (for example 'context window budget'). Terms are split on non-alphanumeric characters and matched case-insensitively against canonical ids, titles, Hooks, and published Section headings and bodies. Section text is searched only when those identity fields produce no candidates, and a body-only match requires every query term. An empty string lists every subject in manifest order."
  14. Changed6 schema fields changed
    • addedInput schema / properties / bound / description
      Added value: +"Maximum candidates per page, 1-8 (default 3)."
    • addedInput schema / properties / cursor / description
      Added value: +"Opaque continuation token from a previous atlas_orient 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 / kind / description
      Added value: +"Restrict candidates to one node kind: 'pattern', 'concept', or 'example'. Roadmap entries carry no kind, so any kind filter excludes them."
    • addedInput schema / properties / query / description
      Added value: +"Ordinary design vocabulary naming the problem or subject (for example 'context window budget'). Terms are split on non-alphanumeric characters and matched case-insensitively; an empty string lists every subject in manifest order."
    • addedInput schema / properties / status / description
      Added value: +"Restrict candidates to one maturity rung of the corpus status ladder; published subjects sit at 'fleshed' or 'stable'."
  15. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Goes well beyond the readOnly/idempotent/non-destructive annotations: it discloses ranking behavior (leading lexical matches preserved, rarer words weigh more), bidirectional reference expansion with via explanations, cursor pagination, that a miss yields an empty page rather than an error, and that bad arguments surface as invalid_argument. This is exactly the extra behavioral context annotations cannot carry.

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 key routing fact ('when you hold no id') and tightly packed, with each sentence carrying real information about ranking, pagination and errors. It is domain-dense (Hooks, via, Roadmap, Release, coherence) and slightly run-on, but nothing is clearly redundant.

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 complex multi-mode search with an output schema already covering return values, the description supplies the routing logic, ranking semantics, pagination contract, and error behavior an agent needs. Nothing required to invoke it correctly is missing.

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 kind, bound, query, cursor and expected_revision are all documented at the field level. The description reinforces a few points (kind leaves Roadmap out, cursor continues a page, via explains connections) but adds little syntax or meaning the schema does not already supply; baseline 3 is appropriate.

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 and resource — find Atlas entries by topic — and immediately scopes the search domain (Nodes, Roadmap entries, Decisions, glossary terms). Crucially it distinguishes itself from the read path: 'an id you already hold can be read directly,' which routes the agent to atlas_read rather than this tool.

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?

Gives a clear triggering condition ('when you hold no id') and an implicit alternative (read directly when you have an id), plus when kind should be set versus omitted. It stops short of naming the sibling tool explicitly, leaving the agent to map 'read directly' onto atlas_read.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources