Skip to main content
Glama
Sign In
atlas-brief-mcp

atlas-brief-mcp

by drproof
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

atlas_links

Read-onlyIdempotent

Inspect a documentation section's linked source files, tags, cross-references, and sibling sections to find which code implements a spec or what references an anchor.

Instructions

Inspect a documentation section's relationships: linked source files (implements), tags, cross-references, and sibling sections.

Use this tool to answer 'which code files implement this spec section?' or 'what other sections
reference or belong to the same document as this anchor?'.

Behavior & Output:
- Read-only lookup against the local section graph and frontmatter metadata (`implements`, `tags`).
- Returns a JSON string `{anchor, heading, path, implements: [...], tags: [...], outgoing_links: [...], incoming_links: [...], siblings: [...]}`
  or `{error}` if the anchor is unknown.

Input Schema

NameRequiredDescriptionDefault
anchorYesSection anchor identifier in `<doc_id>#<section-slug>` or `<doc_id>` format (e.g. 'combat#damage-model'), as returned by `atlas_where`, `atlas_search`, or `atlas_outline`.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.1.1
    • addedInput schema / properties / anchor / description
      Added value: +"Section anchor identifier in `<doc_id>#<section-slug>` or `<doc_id>` format (e.g. 'combat#damage-model'), as returned by `atlas_where`, `atlas_search`, or `atlas_outline`."
    • addedInput schema / properties / anchor / minLength
      Added value: +1
  2. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), and the description goes further by naming the data sources (local section graph plus frontmatter metadata) and the failure mode (`{error}` when the anchor is unknown). The listed return shape is partly redundant with the existing output schema, which caps it below 5.

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?

Purpose is front-loaded in one sentence, then a labelled 'Behavior & Output' block. Every line carries information — sources, return fields, error case — with no filler or restatement of the name.

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 single-parameter read-only lookup with a rich annotation set and a declared output schema, nothing an agent needs is missing: purpose, invocation guidance, data provenance, return shape, and error behavior are all covered.

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 the anchor format and its provenance (atlas_where/atlas_search/atlas_outline) are already documented. The description still adds meaning by disclosing what happens with an invalid anchor — a `{error}` payload — which tells the agent how to interpret results and recover from a bad identifier.

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 ('Inspect') and resource ('a documentation section's relationships'), then enumerates exactly which relations are covered: `implements`, tags, cross-references, siblings. An agent can distinguish this from atlas_read (content) or atlas_search (discovery) without opening any schema.

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?

Frames two concrete question patterns the tool answers ('which code files implement this spec section?', 'what other sections reference or belong to the same document?'), which is a strong usage signal. It does not explicitly name alternatives such as atlas_read or atlas_code_find, so the boundary is implied rather than stated.

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

Deploy Server

Other Tools