Skip to main content
Glama

atlas

Render a one-line-per-component architecture topology from a live board with roles, rationale, verification, flows, and health, or compile a full Markdown specification.

Instructions

Step 1 (Explore LOD_0 or Living Spec): Render the 1-line-per-component Atlas topology (with Charter, Role, Why/Rationale, verification statuses, > FLOW edges, health metrics, and optional Mermaid graph) or pass spec=true to compile the full human-readable Markdown specification from the live board.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "atlas"
  }
}

Input Schema

NameRequiredDescriptionDefault
specNoRender the complete human-readable Markdown specification (Charter, Purpose/Why, Mermaid topology, Flows, Interfaces, Schemas, Laws, Rules) from the live board
boardNoBoard name (default: lattice_core)
boardsNoComma-separated list of board names
mermaidNoInclude Mermaid flowchart
load_allNoLoad all discovered boards
project_rootNoOptional repository root path (auto-discovered by board name or file paths if omitted)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It discloses the two output modes and lists useful content such as Charter, Role, Why/Rationale, verification statuses, FLOW edges, health metrics, and optional Mermaid rendering. However, it does not explicitly state read-only safety, side effects, permissions, or error behavior.

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?

The description is front-loaded with the workflow step and then the two rendering modes. It is dense but efficient; the parenthetical content list is long yet earns its place by specifying what the output includes.

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?

For a six-parameter tool with no output schema and no annotations, the description covers the main modes and output contents well. It leaves parameter interactions such as board versus boards versus load_all to the fully described input schema, which is reasonable given the 100% schema coverage.

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 six parameters. The description reinforces spec=true and optional Mermaid output, but it adds little beyond the schema for board, boards, load_all, or project_root.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives specific verbs ('Render', 'compile') and distinct resources ('Atlas topology', 'human-readable Markdown specification'), and it explains the spec=true mode. It does not explicitly distinguish this tool from any sibling, so it falls short of a 5.

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?

The 'Step 1 (Explore LOD_0 or Living Spec)' framing gives a clear workflow context, and the spec=true path identifies when to request the full specification instead of the topology view. It does not state when not to use the tool or name alternative tools.

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