Skip to main content
Glama

Change Impact

change_impact
Read-only

Reports where-used impact for changed components across a lockfile graph before committing, showing stale consumers and the transitive blast radius.

Instructions

The where-used impact report for a set of changed items over a lockfile graph (issue #142, C3) — surfaces the §9 stale set as an item-level impact report BEFORE a change is committed.

lockfile: path to the lockfile (the §9 dependency graph). changed: the list of changed item / component ids (an ECO's affected set).

Returns {changed, stale (the §9 immediate re-dispatch consumers), where_used (the full transitive blast radius), ok (true iff nothing is impacted)}.

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": {
      "lockfile": "<lockfile>",
      "changed": "<changed>"
    },
    "name": "change_impact"
  }
}

Input Schema

NameRequiredDescriptionDefault
changedYes
lockfileYes
workspaceNoRun this call in this named workspace

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.7
    • addedInput schema / properties / workspace
      Added value: +{
      +  "default": "",
      +  "description": "Run this call in this named workspace",
      +  "title": "Workspace",
      +  "type": "string"
      +}
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds value beyond that by spelling out the return payload (changed, stale, where_used, ok) and the meaning of `ok` — important because there is no output schema. It does not state cost, lockfile-freshness requirements, or failure behavior when the lockfile is missing.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core statement and the return shape, which is good, but the prose is padded with unresolved spec citations (§9, C3, issue #142) that consume space without informing an agent. A tightening pass would drop them and keep the two functional paragraphs.

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

Completeness4/5

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

For a read-only three-parameter query with no output schema, the definition covers inputs, the returned fields, and the pass/fail flag. It leaves open what an agent should do with a non-empty `stale` set, but the core contract needed to invoke the tool correctly is present.

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 description coverage is only 33%, so the description must compensate, and it does: `lockfile` is explained as the path to the dependency graph and `changed` as the ECO affected set of item/component ids. Only the optional `workspace` is left unaddressed, and the schema already documents it.

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 artifact — a where-used impact report computed over a lockfile dependency graph for a set of changed items — and states its timing (before a change is committed). It is distinguishable from the sibling `where_used` only by inference, and the internal references (issue #142, C3, §9) carry no meaning for an agent, which blurs rather than sharpens the statement.

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

Usage Guidelines3/5

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

"BEFORE a change is committed" is a genuine usage signal, but there is no explicit routing: the sibling `where_used` covers overlapping ground and `lifecycle_classify_change` / `lifecycle_apply_change` are adjacent in the change workflow, yet none are named. An agent must guess which one to call.

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

Deploy Server

Other Tools