Skip to main content
Glama

analyze

Read-onlyIdempotent

Produces a full module breakdown of entities, imports, dependents, key entities, layer and boundary files to help coding agents assess architecture and change impact.

Instructions

Full analysis of one module: entities, imports, dependents, key entities, layer and boundary files.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "module": "<module>"
    },
    "name": "analyze"
  }
}

Input Schema

NameRequiredDescriptionDefault
allNoList everything instead of stopping at 200 items.
moduleYesModule ID or file path, as printed by other tools (e.g. src/billing/invoice).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world, so the safety profile is covered elsewhere. The description usefully adds that this is an aggregate view spanning multiple facets rather than a single query. It omits anything about the 200-item truncation implied by the `all` parameter or the cost of a full analysis.

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 and the scope ('one module') placed first. Slightly weakened by loose phrasing ('key entities' repeats 'entities', 'layer and boundary files' is compressed), but nothing is wasted.

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?

No output schema exists, so the description has to carry the return-shape burden; listing the facets partially does this, but the actual structure and the truncation behavior are left undefined. For a read-only aggregating tool with full schema coverage, it is adequate but not sufficient to predict the response.

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 both `module` and `all` are already documented in the schema; baseline 3 applies. The description adds no meaning beyond that — notably it never mentions the 200-item cap or what `all` changes, which is the one piece of context the schema alone states only indirectly.

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?

States a specific resource (one module) and enumerates what the analysis covers: entities, imports, dependents, key entities, layer and boundary files. That enumeration distinguishes it reasonably well from single-facet siblings like deps or boundaries. It falls short of 5 because the word 'analyze' alone is generic and no sibling is named for contrast.

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?

The word 'Full' hints that this is the heavier, comprehensive option versus something like a quick lookup, but the description never says when to choose it over `quick`, `deps`, or `boundaries`. There are no exclusions, prerequisites, or cost/performance guidance to help an agent pick between the many overlapping siblings.

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