Skip to main content
Glama
Sign In
reqtrace-mcp

reqtrace-mcp

by b4ked
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

impact_of_change

Read-only

Identify requirements and tests impacted by code changes since a git ref, listing tests to re-run and reviews invalidated by edits or deletions.

Instructions

Requirements and tests affected by changes since base_ref (a git ref), including requirement text edits and deleted functions. Lists tests to re-run and reviews that the change invalidates.

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_of_change"
  }
}

Input Schema

NameRequiredDescriptionDefault
base_refNoHEAD
include_uncommittedNo

Output Schema

NameRequiredDescriptionDefault
base_refYes
changed_filesYes
changed_itemsYesFunctions/classes/tests touched by the diff
tests_to_rerunYes
include_uncommittedYes
reviews_invalidatedYes
affected_requirementsYesreq id -> reasons

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare this is a safe, read-only, closed-world operation, so the safety burden is covered. The description adds real behavioral detail beyond that (it detects requirement text edits and deleted functions, and reports invalidated reviews), but says nothing about defaults, scope, or cost despite the two documented defaults in the schema.

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 sentences, no filler, with the core purpose front-loaded and the output content appended. The parenthetical about base_ref is well placed, though the second sentence slightly overlaps the first.

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?

An output schema exists, so return values need not be described, and annotations cover the safety profile. What remains thin is orientation: no guidance on when this beats trace_matrix or coverage_report, and no note on the effect of the uncommitted-changes flag, for a tool that is clearly a multi-input repository analysis.

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 0%, so the description must carry parameter meaning. It clarifies base_ref as 'a git ref' and pins the comparison window ('since base_ref'), which is genuine added value, but include_uncommitted is entirely unexplained in both schema and description, and the HEAD default is not addressed.

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 description states a specific analysis verb and its object: requirements and tests affected by changes since a git ref, including text edits and deleted functions. It is concrete and unambiguous on its own, but it never names or distinguishes itself from overlapping siblings such as trace_matrix or coverage_report.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: the phrase 'Lists tests to re-run and reviews that the change invalidates' signals this is a post-change impact analysis. There is no explicit when-to-use, no prerequisites (e.g., must be run in a repo), and no routing to or away from the sibling analysis tools.

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

Deploy Server

Other Tools