Skip to main content
Glama

check_file_impact

Assess a file's change impact by checking its hub size and direct callers; read the decision first, and use includeAffected to list affected modules.

Instructions

Hub size and the direct callers of one file. 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": {
      "path": "<path>"
    },
    "name": "check_file_impact"
  }
}

Input Schema

NameRequiredDescriptionDefault
maxNo
fileNo
pathYes
repoNo
includeAffectedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/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 burden. It does disclose the "high" threshold behavior (count over max) and that includeAffected expands to the full module list, which is useful behavioral context, but it says nothing about read-only status, permissions, error handling, or what is actually returned.

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 front-loaded and free of fluff, with purpose stated first. But the telegraphic fragments and unexplained reference ("Read decision first") make it feel under-specified rather than genuinely concise for a five-parameter tool.

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?

A five-parameter tool with 0% schema coverage, no annotations, and no output schema needs a far richer description. Two parameters and the "high" output semantics are covered, but three parameters and the return shape remain undocumented, leaving clear gaps.

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 coverage is 0%, so the description must compensate for all five parameters. It adds meaning only for includeAffected (full module list) and max (threshold for "high"), leaving path, file, and repo completely undefined, including the ambiguous path-vs-file distinction.

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

Purpose3/5

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

The phrase "Hub size and the direct callers of one file" names the resource (a single file) and the outputs (hub size, caller count), which lets an agent distinguish this from check_diff_impact. But it's a noun phrase rather than a verb and "hub size" is never defined, so the exact action/computation remains vague.

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?

There is implied workflow guidance ("Read decision first") and a conditional parameter rule ("Pass includeAffected only for the full module list"), which tells the agent when to add expansion. However, no sibling tool is named and "Read decision first" references an unexplained concept, so when/when-not guidance is only inferred.

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