atlas-brief-mcp

Overview Schema Source Related Servers Discussions Admin

atlas_status

Read-onlyIdempotent

Return the authoritative list of Work Orders with statuses (open, in progress, done) and index freshness in one read-only call to check project progress or find the next work order.

Instructions

Return the complete list of documented Work Orders (⬜ OPEN, 🚧 IN PROGRESS, ✅ DONE) and index freshness.

Takes no parameters. Use this tool first when asked about project progress, completed milestones,
or which Work Order is next — one call returns the authoritative list without reading documentation files.
For granular Markdown checkboxes (`- [ ]`), use `atlas_tasks` instead.

Behavior & Output:
- Read-only query over all Work Order headings/entries in the index (up to 60 orders).
- Returns a human- and agent-readable summary starting with the index freshness timestamp,
  total counts (`done` / `open`), and one line per Work Order (`WO # — status — title (anchor)`).

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 5, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the description doesn't need to re-litigate safety. It adds real context beyond them: the operation is a read-only index query capped at up to 60 orders, and the output begins with an index freshness timestamp that signals possible staleness.

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 core purpose, then when-to-use, then a labeled 'Behavior & Output' block — a clean structure. Slightly long for a zero-parameter tool, and the status emoji list is mildly redundant with the status names, but every section carries usable information.

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?

Complete enough to call correctly: it covers trigger conditions, the sibling boundary, the 60-order cap, and the return shape. The one gap is that the description explains the output format even though a formal output schema exists, which is mild duplication rather than a missing piece.

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?

The tool takes zero parameters, so the baseline is 4; the description confirms 'Takes no parameters', which prevents an agent from searching for filters. Nothing further is needed since there is no schema surface to explain.

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 ('Return the complete list of documented Work Orders') and enumerates the status values it reports, plus index freshness. It also explicitly distinguishes itself from the sibling atlas_tasks, which handles granular Markdown checkboxes.

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

Usage Guidelines5/5

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

Gives an explicit when-to-use rule ('Use this tool first when asked about project progress, completed milestones, or which Work Order is next') and an explicit alternative for the adjacent case ('For granular Markdown checkboxes, use atlas_tasks instead'). The no-parameter constraint is also stated.

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

Deploy Server