Skip to main content
Glama

Impact Analysis

impact_analysis

Calculate direct and transitive downstream files affected when a file changes, helping you assess modification impact before editing.

Instructions

Calculate direct and transitive downstream files affected if a given file is modified.

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": {
      "file_path": "<file_path>"
    },
    "name": "impact_analysis"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNo.
file_pathYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations, the description carries the full disclosure burden. It communicates the key behavioral trait that the analysis is transitive, but says nothing about how dependencies are resolved, whether the operation is read-only, its cost on large codebases, or failure modes for unknown files.

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 no redundant restatement of the title. It is efficient, though its brevity edges into under-specification rather than pure conciseness.

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

Completeness2/5

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

An output schema exists, so return values needn't be explained, but for a two-parameter analysis tool with 0% schema coverage the description omits the meaning of 'path' and all behavioral context. The definition leaves real gaps for correct invocation.

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 description must compensate, and it only covers file_path implicitly. The second parameter, 'path' with default '.', is never mentioned, leaving the agent to guess whether it is a project root or an alternate file locator.

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 action ('Calculate') and a specific output ('direct and transitive downstream files affected'), plus the triggering condition ('if a given file is modified'). An agent can distinguish this from read_file or write_file easily, though it doesn't explicitly contrast with the closest sibling, build_dependency_graph.

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 guidance on when to use this versus alternatives such as build_dependency_graph or verify_work, nor any prerequisites (e.g., whether a dependency index must exist first). The only implicit cue is that you need a file that will be modified, which is not enough for confident tool selection.

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