Skip to main content
Glama

weavegraph_blast_radius

Computes the shortest-hop transitive blast radius from changed seed files to show affected code before edits.

Instructions

Compute shortest-hop transitive blast radius from changed seed files.

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": {
      "repo_path": "<repo_path>",
      "seed_files": "<seed_files>"
    },
    "name": "weavegraph_blast_radius"
  }
}

Input Schema

NameRequiredDescriptionDefault
repo_pathYes
seed_filesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full disclosure burden, yet it says nothing about whether the operation mutates anything, what permissions or repo state it requires, or how expensive a whole-repo traversal is. The single adjective "shortest-hop" hints at a BFS-style traversal but does not describe behavior the agent can rely on.

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?

One front-loaded sentence with no filler and the key qualifier ("shortest-hop transitive") placed before the resource. It is efficient, though the terseness leaves gaps that a slightly longer definition would need to fill.

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?

For a graph-traversal tool with two undocumented parameters, no annotations, and no output schema, the definition should say what the blast radius is returned as (affected paths, hop distances, or a graph) and what preconditions hold. None of that is present, so an agent cannot predict the result shape or cost before calling.

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 define both parameters. It clarifies that seed_files are "changed seed files" driving the traversal, but never explains repo_path, nor whether seed paths are absolute, relative to repo_path, or must already exist in an index.

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 ("Compute") and a specific analytic output ("shortest-hop transitive blast radius") scoped to "changed seed files", which is enough to tell it is an impact/ripple analysis rather than indexing or merge verification. It stops short of explicitly contrasting itself with the siblings, and "blast radius" is domain jargon an agent must interpret.

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?

There is no when-to-use guidance, no stated prerequisite (e.g. that the repo must be indexed first), and no mention of any alternative tool for related impact questions. The agent is left to infer timing and sequencing entirely on its own.

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