Skip to main content
Glama

architecture_status

Returns a read-only session map of primary language, top hubs, open boundaries, and unresolved file count when impact hooks did not run or the caller set is unknown.

Instructions

Session map: primary language, top hubs, open boundaries, and the unresolved file count. Call this when impact hooks did not run or the caller set is unknown. Writes nothing.

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": "architecture_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
repoNo

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 burden, and it does disclose the two most important traits: it writes nothing, and it returns a bounded set of summary fields. It says nothing about cost, permissions, error behavior, or whether the scan is expensive on large repos, so it is only partially transparent.

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?

Three short clauses, front-loaded with what the caller gets, then the trigger condition, then the safety note. There is no filler and nothing to trim.

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 one-optional-parameter read tool with no output schema, the description covers purpose, trigger, and read-only nature well. The only real omission is the meaning and scoping of the repo parameter, which leaves an agent guessing about target selection.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% and the single parameter (repo) is never mentioned in the description. An agent cannot tell whether repo is required, whether it defaults to the current session, or what form it takes, and the description does not compensate for the schema gap.

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 names a concrete artifact (a session map) and enumerates its contents: primary language, top hubs, open boundaries, unresolved file count. That is specific enough to distinguish it from the impact-checking siblings, though it never names them, so the contrast is left implicit.

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 an explicit trigger: call this when impact hooks did not run or the caller set is unknown. That is a clear when-to-use condition tied to a failure mode of the sibling tools. It does not state when-not to call it (e.g. when impact data is already available), so it stops short of full routing guidance.

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