Skip to main content
Glama
Sign In
ast-impact-mapper-mcp

ast-impact-mapper-mcp

by vola-trebla
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_rename_aware_diff

Identify affected tests in TypeScript projects while correctly handling renamed and moved files, using rename detection and ignoring whitespace-only changes.

Instructions

Like get_affected_tests_by_branch, but correctly handles renamed and moved files. Uses --find-renames to detect file moves and --ignore-all-space to skip whitespace-only changes. Use instead of get_affected_tests_by_branch when the branch contains refactors or file moves.

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": {
      "project_root": "<project_root>"
    },
    "name": "get_rename_aware_diff"
  }
}

Input Schema

NameRequiredDescriptionDefault
base_branchNoBranch to diff against (default: main)main
project_rootYesAbsolute path to the TypeScript project root (must contain tsconfig.json)
similarity_thresholdNoMinimum similarity % to consider a file move a rename (default: 90)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden. It discloses the use of --find-renames and --ignore-all-space, which explains behavior beyond the name. However, it does not mention whether the operation is read-only or any side effects, which would be useful given the lack of annotations.

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?

The description is three sentences: a comparison, a technical detail sentence, and a usage directive. Every sentence adds value, and the most important information is front-loaded. No fluff or redundancy.

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?

The tool has no output schema and no annotations, so the description should ideally clarify what the tool returns. It implies the return matches get_affected_tests_by_branch ('Like...'), which supports inference, but does not explicitly state the output. The core functionality and usage context are well covered, making this only a minor gap.

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 schema already has 100% coverage for all parameters, so the baseline is 3. The description adds no extra parameter-specific meaning beyond what the schema provides; the similarity_threshold is already well-documented in the schema.

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?

The description clearly states the tool computes affected tests while handling renamed and moved files, distinguishing it from the sibling get_affected_tests_by_branch. It names the exact comparison and the specific behavior that sets it apart (rename/move handling).

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 says 'Use instead of get_affected_tests_by_branch when the branch contains refactors or file moves,' providing clear when-to-use guidance and naming the alternative tool. This directly answers the selection problem.

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