Skip to main content
Glama

repo_impact

Read-onlyIdempotent

Show direct dependencies, dependents, and historical coupling for a file or module to gauge change impact. Use it before refactoring to see what else may break.

Instructions

Show direct dependencies, dependents, and historical coupling.

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": {
      "path": "<path>"
    },
    "name": "repo_impact"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.6

TDQS

B3/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 scope, so the safety profile is fully covered. The description adds the useful detail that results combine forward dependencies, reverse dependents, and historical coupling in one view. It says nothing about cost, depth, or whether coupling is computed from commit history, which would help an agent predict latency and output shape.

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?

One short sentence with zero filler, front-loaded on the verb and the three result categories. It is efficient, though the terseness comes at the cost of the missing parameter and scope detail noted elsewhere.

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?

For a single-parameter, read-only, closed-world tool with no output schema and full annotation coverage, only a modest description is needed. The listed output categories are helpful, but the undefined meaning of 'path' and the absent sibling differentiation leave real gaps an agent must resolve by trial.

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 description coverage is 0%, so the single required parameter 'path' is documented nowhere. The description does not clarify whether path refers to a file, a directory, a module, or a repository root, nor whether it is absolute or repo-relative — a meaningful gap for a tool whose entire scope hinges on that argument.

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 and three concrete outputs: direct dependencies, dependents, and historical coupling. An agent can form a clear picture of what the tool returns, but nothing distinguishes it from similarly named siblings such as repo_dependencies, repo_graph, or repo_history.

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 when-to-use guidance, no exclusions, and no mention of any alternative. The agent is left to guess whether this is the right tool versus repo_dependencies or repo_graph when it needs dependency information.

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