Skip to main content
Glama

Compute 1-Hop AST Reverse-Dependency Blast Radius

nomos_verify_impact
Read-onlyIdempotent

Computes the deterministic 1-hop AST reverse-dependency blast radius of packages affected by uncommitted or branch-modified files, showing which downstream packages and test suites your edits impact.

Instructions

Compute the deterministic 1-hop AST reverse-dependency blast radius of packages impacted by uncommitted or branch-modified files. Use when assessing which downstream packages and test suites are affected by current edits. Do NOT use when auditing full-repository structural complexity or AI Hangover Score (use nomos_xray instead).

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": "nomos_verify_impact"
  }
}

Input Schema

NameRequiredDescriptionDefault
dirNoTarget repository root or subdirectory path (defaults to current working directory)..

Output Schema

NameRequiredDescriptionDefault
dirYesResolved repository root path.
impacted_packagesYesImpacted package paths.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower; the description still adds real behavior: the analysis is deterministic, limited to exactly one hop, and scoped to the working-tree/branch delta rather than the whole repository. It does not say what happens on a clean tree or how the base branch is chosen, which is a modest remaining gap given an output schema exists.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, all load-bearing: what it computes, when to use it, when to use something else. Scope and exclusion are front-loaded with zero filler or restated title text.

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

Completeness5/5

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

For a one-parameter read-only tool with rich annotations and an output schema, the description supplies everything an agent needs to choose it: the analysis boundary, the input class, and the sibling to prefer for a different kind of audit. Return values need not be explained because the output schema covers them.

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?

The single parameter 'dir' has 100% schema coverage including a default and examples, so the schema carries the semantics. The description never mentions the directory argument or its default, adding no meaning beyond the schema. Baseline 3 applies.

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?

States a specific verb ('Compute') and a precisely bounded resource ('1-hop AST reverse-dependency blast radius'), plus the input class ('uncommitted or branch-modified files'). This is distinct enough that an agent can separate it from nomos_xray without opening either schema.

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

Usage Guidelines5/5

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

Explicitly names the when-to-use case ('assessing which downstream packages and test suites are affected by current edits') and the when-not case ('auditing full-repository structural complexity or AI Hangover Score'), and routes to the named alternative nomos_xray. Nothing is left to inference.

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