Skip to main content
Glama

Guard Impact Analysis

codapult_guard_impact

Trace the likely project impact of changed files through dependency graphs before editing, revealing dependents, routes, capabilities, contracts, and graph paths to inspect.

Instructions

Trace the likely project impact of one or more file paths through the discovered dependency graph, including dependents, routes, capabilities, contracts, and graph paths. Use before changing a file to understand downstream areas to inspect. This is repository analysis, not a policy pass/fail check; returns structured impact details.

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": {
      "files": "<files>"
    },
    "name": "codapult_guard_impact"
  }
}

Input Schema

NameRequiredDescriptionDefault
rootNoProject path or workspace root.
filesYesRepository-relative paths to analyze; provide every changed or planned file of interest.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.13.2
    • addedInput schema / properties / files / description
      Added value: +"Repository-relative paths to analyze; provide every changed or planned file of interest."
  2. First observed

TDQS

A3.6/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 disclosure burden. It does establish that this is a read-only analysis pass rather than a pass/fail gate and that it returns structured details, but it omits prerequisites (the graph is 'discovered' — does init/analyze need to run first?), behavior for unknown or unindexed paths, and any cost or scope limits.

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?

Three tight sentences, front-loaded with the core action and followed by the usage trigger and the disambiguation clause. No filler, though the output-category list is slightly dense.

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?

There is no output schema, so the description usefully previews the return shape by naming the impact categories it reports. Combined with the usage trigger this is nearly complete for a two-parameter analysis tool; only the dependency on a pre-built graph is left implicit.

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

Parameters3/5

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

Schema description coverage is 100%, so both `root` and `files` are already documented in the schema. The description only echoes the array semantics ('one or more file paths'), adding no format, path-resolution, or multi-file interaction detail beyond what the schema provides; baseline 3 applies.

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?

States a specific verb and resource ('Trace the likely project impact of ... file paths through the discovered dependency graph') and enumerates the output categories (dependents, routes, capabilities, contracts, graph paths). It also draws a category-level boundary against policy tools ('not a policy pass/fail check'), though it never names a specific sibling such as codapult_guard_check or codapult_guard_analyze.

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

Usage Guidelines4/5

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

'Use before changing a file to understand downstream areas to inspect' gives an explicit trigger condition. The negative framing ('repository analysis, not a policy pass/fail check') steers the agent away from the verification siblings, but no alternative tool is named for the case where a policy answer is actually wanted.

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