claude-engram

Overview Schema Source Related Servers Discussions Admin

impact_analyze

Analyze how code changes affect your project by identifying dependents, exports, and risk levels. Evaluate proposed modifications before implementing to prevent unintended consequences.

Instructions

Analyze change impact. Shows dependents, exports, risk level.

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>",
      "project_root": "<project_root>"
    },
    "name": "impact_analyze"
  }
}

Input Schema

Name	Required	Description	Default
`file_path`	Yes
`project_root`	Yes
`proposed_changes`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Apr 26, 2026

TDQS

C2.8/5.0

Behavior2/5

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

No annotations exist, and the description only lists outputs but does not disclose side effects, mutability, authentication needs, rate limits, or output format.

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?

Extremely concise at two sentences, but lacks crucial details. Still, no wasted words.

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?

Given the tool's complexity (change impact analysis), the description omits output schema, interpretation of risk level, and limitations. Incomplete for practical use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, yet the description does not explain any parameter meanings or acceptable values for file_path, project_root, or proposed_changes.

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?

The description clearly states the tool analyzes change impact and shows dependents, exports, and risk level. This distinguishes it from sibling tools like scout_analyze or deps_map.

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?

No information on when to use this tool versus alternatives, or when not to use it. No prerequisites or context provided.

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