Skip to main content
Glama

check_scar_tissue

Checks historical dead ends before editing a target file and returns short redline alerts when the file, symbol, or planned change matches a prior failed approach.

Instructions

Mandatory pre-edit Gatekeeper: Check historical dead ends before modifying target_file.

Instead of dumping thousands of lines of CLAUDE.md history into the context window, returns strictly <= 50-char high-priority redline alerts ONLY when the target file, symbol, or 16-dim semantic intent matches a historical minefield.

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": {
      "target_file": "<target_file>"
    },
    "name": "check_scar_tissue"
  }
}

Input Schema

NameRequiredDescriptionDefault
top_kNo
thresholdNo
target_fileYes
target_symbolNo
planned_changeNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the burden and usefully discloses the output behavior: strict <=50-character redline alerts only when the file, symbol, or semantic intent matches a historical minefield. It also explains the rationale of avoiding context-window dumping, though it does not explicitly state read-only side effects or permissions.

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 front-loaded with the mandatory pre-edit role, then immediately qualifies the output and matching behavior. Two sentences do the work without filler.

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?

The purpose, usage timing, and output filtering are sufficiently described, and an output schema exists so return structure need not be repeated. However, for a five-parameter tool with no annotations and zero schema description coverage, the missing explanations of `top_k`, `threshold`, and `planned_change` leave meaningful gaps.

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 description coverage is 0%, so the description must compensate for five undocumented parameters. It mentions `target_file`, `target_symbol`, and semantic intent indirectly, but does not explain `top_k`, `threshold`, or `planned_change`, leaving important tuning and matching parameters opaque.

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 verb and resource: checking historical dead ends before modifying `target_file`, framed as a mandatory pre-edit gatekeeper. It is clear and concrete, but it does not explicitly compare itself with the sibling recording tool, so sibling differentiation is only implied.

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

Usage Guidelines4/5

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

It clearly says this is mandatory before modifying `target_file`, which gives strong when-to-use guidance. It does not state when not to use it or explicitly name an alternative tool, leaving some routing context implicit.

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