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

atlas-brief-mcp

by drproof
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

atlas_brief

Read-onlyIdempotent

Assemble a self-contained Markdown task brief with relevant spec sections, source paths, open tasks, guardrails, and the checkoff command before delegating a coding feature.

Instructions

Assemble a self-contained Markdown task brief for a coding agent or subagent.

Use this tool before starting or delegating a feature task. It bundles the top matching spec
sections (with stable anchors), linked source file paths, open tasks, project guardrails, and
the verified checkoff command so the subagent does not need to search from scratch.

Behavior & Output:
- Read-only aggregation of indexed documentation sections and code metadata.
- Returns a formatted Markdown brief string ready to paste into a subagent prompt.

Input Schema

NameRequiredDescriptionDefault
goalYesOne-sentence description of the task to prepare a brief for (e.g. 'wire the dwarf vault-charger perk into turn_manager').
filesNoOptional list of relative source file paths to include alongside auto-detected `implements` files (e.g. ['scripts/unit.gd', 'src/combat.py']).
work_orderNoOptional Work Order number (e.g. 7). When provided, the brief includes the exact `atlas_publish` / `atlas_set_status` closing command for that Work Order.
max_sectionsNoMaximum number of relevant documentation sections to embed in the brief (1-20, default 5).

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv0.1.1
    • addedInput schema / properties / files / description
      Added value: +"Optional list of relative source file paths to include alongside auto-detected `implements` files (e.g. ['scripts/unit.gd', 'src/combat.py'])."
    • addedInput schema / properties / goal / description
      Added value: +"One-sentence description of the task to prepare a brief for (e.g. 'wire the dwarf vault-charger perk into turn_manager')."
    • addedInput schema / properties / goal / minLength
      Added value: +1
    • addedInput schema / properties / max_sections / description
      Added value: +"Maximum number of relevant documentation sections to embed in the brief (1-20, default 5)."
    • addedInput schema / properties / max_sections / maximum
      Added value: +20
    • addedInput schema / properties / max_sections / minimum
      Added value: +1
    • changedInput schema / properties / work_order / anyOf
      Previous value: -[
-  {
-    "type": "integer"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "minimum": 1,
+    "type": "integer"
+  },
+  {
+    "type": "null"
+  }
+]
    • addedInput schema / properties / work_order / description
      Added value: +"Optional Work Order number (e.g. 7). When provided, the brief includes the exact `atlas_publish` / `atlas_set_status` closing command for that Work Order."
  2. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Beyond the read-only/idempotent annotations, it explains that the tool performs read-only aggregation of indexed documentation and code metadata and returns a formatted Markdown string ready to paste into a prompt. That adds useful behavioral context, though it does not discuss limitations or edge cases.

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 front-loaded with the core purpose, followed by usage and behavior/output sections. Every sentence adds useful context without unnecessary repetition.

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?

Given that the tool has an output schema and full schema coverage, the description provides enough context: what gets bundled, when to use it, and what the output is. Nothing essential for correct invocation appears 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 the schema already documents all four parameters thoroughly. The description does not add parameter-specific meaning beyond what the schema provides, which is the expected baseline.

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 verb and resource: 'Assemble a self-contained Markdown task brief for a coding agent or subagent.' It also clarifies the aggregation scope (spec sections, source paths, open tasks, guardrails, checkoff command), making it distinct from search/read siblings.

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?

It gives clear timing guidance: 'Use this tool before starting or delegating a feature task,' and implies the alternative is searching from scratch. It stops short of explicit when-not-to-use conditions or naming sibling tools directly.

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