Skip to main content
Glama
GodPrompt MCP Server

GodPrompt MCP Server

Trace changed-code impact and test coverage

trace_change_impact
Read-onlyIdempotent

Rank files affected by code changes and select relevant tests using caller-supplied dependency, requirement, and receipt evidence to plan test scope.

Instructions

Rank affected files and select test cases with explicit dependency and requirement-to-test mappings. All graph and receipt evidence must be supplied by caller; no repository or command execution.

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": {
      "changed_files": "<changed_files>"
    },
    "name": "trace_change_impact"
  }
}

Input Schema

NameRequiredDescriptionDefault
testsNo
receiptsNo
dependenciesNo
requirementsNo
changed_filesYes

Output Schema

NameRequiredDescriptionDefault
issuesYes
statusYes
warningYes
truncatedYes
affected_filesYes
tests_executedYes
recommended_testsYes
uncovered_targetsYes
independently_verifiedYes
impacted_requirement_idsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.4.2

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly/openWorld=false/idempotent/non-destructive, so the safety profile is known. The description adds genuinely non-obvious behavior: this is a pure computation over caller-supplied evidence with no repository access or command execution, which changes how an agent must prepare inputs. It stops short of stating determinism or how ties are ranked.

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?

Two sentences, zero filler, and the primary action is front-loaded ahead of the input-supply constraint. Every clause carries distinct information.

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?

An output schema exists, so return-value shape need not be described, and annotations cover the safety profile. Still, for a five-parameter analytical tool the description omits what happens with incomplete evidence (e.g., a receipt for an unknown test, or files with no declared dependencies) and how ranking is determined—gaps an agent would care about before calling.

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 schema supplies only patterns and bounds, not meaning. The description partially compensates by naming the required evidence classes—graph (dependencies), receipts, requirement-to-test mappings, and changed files—which conceptually maps to all five parameters. It does not explain semantics such as what a receipt status implies, how covers_files interacts with requirements.files, or how ranking is computed.

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?

Uses specific verbs and resources: 'rank affected files' and 'select test cases' using 'dependency and requirement-to-test mappings'. That is distinct from siblings like build_test_matrix or review_code_change, though no sibling is named explicitly to sharpen the contrast.

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?

The clause 'All graph and receipt evidence must be supplied by caller; no repository or command execution' functions as a precondition for calling the tool, which is useful. However, there is no explicit statement of when to prefer this over build_test_matrix or review_code_change, nor any exclusion beyond the no-execution constraint.

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