Skip to main content
Glama

Change impact

change_impact
Read-onlyIdempotent

Identify files, symbols, and tests affected by planned code changes so you know what to read and which tests to run before renaming or editing.

Instructions

List the files and symbols affected by changing given files or symbols (direction: dependents, dependencies or both). At least one of files/symbols; a symbol seed takes {name, relative_path} (file is an alias). Use when: you are about to rename or change something and need which files to read and which tests to run. Avoid when: you want the whole graph (dependency_graph). Output: affected[] {id, distance, path, confidence}, summary {affected_files, affected_symbols, tests_affected}, unresolved[] (the seeds that did not resolve: symbol, reason, next_step), stats {unresolved_imports, min_confidence, filtered_possible}. By default only exact/likely edges are traversed; pass min_confidence="possible" to follow name-matching guesses.

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

Input Schema

NameRequiredDescriptionDefault
depthNoMax hops from the seeds (default 5).
filesNoWorkspace paths you plan to edit. At least one of files/symbols is required.
formatNoOutput format (default json).
symbolsNoSymbols you plan to rename/change; pass a name, or {name, relative_path} (or {name, file}) when the name is ambiguous. At least one of files/symbols is required.
directionNoTraversal direction (default dependents).
max_nodesNoMax affected files (default 300).
include_testsNotrue includes test files (default) and counts them in tests_affected.
min_confidenceNoOnly traverse edges at or above this confidence (default "likely"). "exact" = import/declared-in-one-file ties; "likely" = unique name match; "possible" = name matched several declarations (noisy at distance >= 2). Skipped edges are counted in stats.filtered_possible.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv4.5.0
    • removedInput schema / properties / include_tests / anyOf
      Removed value: -[
      -  {
      -    "type": "boolean"
      -  },
      -  {
      -    "maximum": 1,
      -    "minimum": 0,
      -    "type": "integer"
      -  }
      -]
    • changedInput schema / properties / include_tests / description
      Previous value: -"1 includes test files (default) and counts them in tests_affected."New value: +"true includes test files (default) and counts them in tests_affected."
    • removedInput schema / properties / include_tests / maximum
      Removed value: -1
    • removedInput schema / properties / include_tests / minimum
      Removed value: -0
    • changedInput schema / properties / include_tests / type
      Previous value: -"integer"New value: +"boolean"
  2. Changed1 schema field changedv4.1.0
    • addedInput schema / properties / min_confidence
      Added value: +{
      +  "description": "Only traverse edges at or above this confidence (default \"likely\"). \"exact\" = import/declared-in-one-file ties; \"likely\" = unique name match; \"possible\" = name matched several declarations (noisy at distance >= 2). Skipped edges are counted in stats.filtered_possible.",
      +  "enum": [
      +    "exact",
      +    "likely",
      +    "possible"
      +  ],
      +  "type": "string"
      +}
  3. Addedv4.0.0

TDQS

A4.9/5.0
Behavior5/5

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

Annotations only declare readOnly/idempotent/closed-world; the description goes further by disclosing traversal defaults (exact/likely edges only), the noise tradeoff of min_confidence="possible", and how filtered edges are accounted for in stats.filtered_possible. It also explains seed-resolution failure handling via unresolved[] with a next_step field, which is behavior an agent cannot infer from annotations.

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?

Front-loaded with the operation, then a labeled Use when / Avoid when / Output structure that lets an agent scan for the relevant part. Every clause carries information — parentheticals are used for defaults and aliases rather than as filler.

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

Completeness5/5

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

With 8 parameters and no output schema, the description carries the return shape itself (affected[], summary, unresolved[], stats) and explains the defaults that materially change results (direction, min_confidence, include_tests). Nothing an agent needs in order to invoke it correctly or interpret the result is missing.

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?

Schema coverage is 100%, so the baseline is 3, and the description adds genuine meaning: the shorthand that a symbol seed takes {name, relative_path} with file as an alias, and the practical rule for when to pass min_confidence="possible". It stops short of advising on depth or max_nodes tradeoffs, so it is not fully additive.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("List the files and symbols affected by changing given files or symbols") plus the direction dimension, so the agent knows exactly what is returned. It also distinguishes itself from the sibling dependency_graph, which returns the whole graph rather than a scoped blast radius.

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

Usage Guidelines5/5

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

Explicit "Use when: you are about to rename or change something and need which files to read and which tests to run" gives a concrete triggering scenario. "Avoid when: you want the whole graph (dependency_graph)" names the alternative and the condition that selects it.

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