Skip to main content
Glama

impact

Trace user stories and acceptance criteria affected by changed files or a git diff range, with weakest-edge confidence for each, to assess a change's blast radius.

Instructions

Blast radius of a change: the stories and acceptance criteria that depend on the given files (or the files in a git diff range), each tagged with its weakest-edge confidence. Pass either files or diff, not both.

Prefer brief=true: a bounded answer with the stories grouped by feature, their acceptance criteria and the files that reach them, without entity lists. With feature set to the feature you are working on, the stories of other features come first (other_features) — the ones a change breaks unnoticed.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "impact"
  }
}

Input Schema

NameRequiredDescriptionDefault
diffNo
repoNo.
briefNo
filesNo
featureNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.8.0
    • addedInput schema / properties / brief
      Added value: +{
      +  "default": false,
      +  "title": "Brief",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / feature
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Feature"
      +}
  2. First observedv0.3.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It does disclose output behavior well — grouping by feature, 'weakest-edge confidence' tagging, omitting entity lists under brief, and the `other_features` ordering — but says nothing about read-only/ side-effect status, cost or scan scope, or failure modes when neither input matches.

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?

Two tight paragraphs: the first states what is computed and the input constraint, the second states the recommended usage. Front-loaded and largely waste-free, with only mild jargon ('weakest-edge confidence') that isn't defined.

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

Completeness3/5

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

For a five-parameter tool with no annotations and no output schema, the description does a fair job of sketching the return shape and the brief/feature modes. It falls short on the undocumented `repo` parameter, expected cost/size of the analysis, and what happens with empty or ambiguous input.

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 coverage is 0%, so the description must carry parameter meaning. It covers the `files`/`diff` mutual exclusivity, the `brief` tradeoff, and the `feature` grouping effect, which is real value, but `repo` is never mentioned and no format/example is given for file paths or the diff range syntax.

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 opening clause names the concept ('blast radius of a change') and the concrete resource returned: 'the stories and acceptance criteria that depend on the given files (or the files in a git `diff` range)'. That is specific enough for an agent to know exactly what question this tool answers, though it never contrasts itself with sibling tools such as story_trace or staleness.

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?

It gives a hard input rule ('Pass either `files` or `diff`, not both') and a positive default recommendation ('Prefer `brief=true`'), plus when to set `feature`. What's missing is any when-not guidance or routing away from sibling analysis tools, so the guidance is clear but not exhaustive.

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