Skip to main content
Glama

repo_architecture

Read-onlyIdempotent

Summarizes repository languages, modules, and graph relationships to help coding agents understand codebase structure and navigate architecture.

Instructions

Summarize repository languages, modules, and graph relationships.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.6

TDQS

B3.1/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false, and destructiveHint=false, so the safety profile is fully covered. The description adds no behavioral context beyond that — no indication of scope (entire repository vs. current workspace), depth of summarization, size of output, or whether it is expensive on large repos.

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?

A single front-loaded sentence with no filler. It is slightly under-specified rather than verbose, which is not a conciseness failure.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is cheap to call and has no parameters, but there is no output schema, so the description is the only source of return-value expectations. It lists the three content categories but says nothing about the structure, granularity, or scale of the summary an agent will receive.

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 of 4 applies. The description correctly implies no inputs are needed to invoke it, and nothing is misrepresented.

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 specific verb ('Summarize') and concrete resource content ('repository languages, modules, and graph relationships'), so an agent knows what it produces. It does not, however, distinguish this from siblings such as repo_graph, repo_dependencies, or repo_context, which plausibly overlap on the graph/relationship portion.

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

Usage Guidelines2/5

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

There is no statement of when to use this versus repo_graph or repo_dependencies, no prerequisites, and no exclusions. The agent must infer from the word 'Summarize' that this is a high-level overview rather than a detailed graph query.

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