Skip to main content
Glama

check_diff_impact

Calculate the blast radius and direct callers of changed files before merging; use the decision signal to flag high impact and optionally list full affected modules.

Instructions

Combined blast radius and the direct callers of the changed files. Read decision first. high means the count is over max. Pass includeAffected only for the full module list.

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": {
      "paths": "<paths>"
    },
    "name": "check_diff_impact"
  }
}

Input Schema

NameRequiredDescriptionDefault
maxNo
repoNo
filesNo
pathsYes
includeAffectedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose some behavior: output includes blast radius, callers, and a decision; 'high' means the count exceeds max; includeAffected changes whether the full module list is returned. However, it does not explicitly confirm read-only behavior, permissions, side effects, or response structure.

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?

The description is very short and front-loads the output concepts, but it is written in terse fragments and uses ambiguous references such as 'decision' and 'count'. It is not padded, yet its structure makes the meaning harder to parse than necessary.

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?

This is a five-parameter tool with no annotations and no output schema, so the description needs to compensate more than it does. It covers the high-level output and two parameters, but leaves most parameter semantics and the full return behavior undocumented.

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 explain all five parameters, but it only adds meaning for max ('high means the count is over max') and includeAffected ('only for the full module list'). The required paths parameter and the repo and files parameters receive no explanation.

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 states that the tool returns combined blast radius and direct callers of changed files, which gives a clear resource and output focus. It does not explicitly differentiate itself from sibling tools such as check_file_impact, but the purpose is understandable without opening the schema.

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 description offers only fragmentary usage guidance: 'Read decision first' and the conditional for includeAffected. It never states when to use this tool instead of check_file_impact, architecture_status, or plan_fix, and gives no exclusions or prerequisites for the tool as a whole.

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