Skip to main content
Glama

record_dead_end

Records proven dead-end code changes with root cause and safe pivot, then generates a short warning to prevent repeating failed approaches in matching files or modules.

Instructions

Record a proven dead-end code change (Anti-Memory / Scar Tissue).

Extracts {attempted_change + error_root_cause + dead_end_approach + safe_pivot}, encodes a 16-dimensional latent scar vector (Memorilla-inspired gatekeeper), and compiles a strictly <= 50 character Contrastive Pivot redline alert.

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>",
      "attempted_change": "<attempted_change>",
      "error_root_cause": "<error_root_cause>",
      "dead_end_approach": "<dead_end_approach>"
    },
    "name": "record_dead_end"
  }
}

Input Schema

NameRequiredDescriptionDefault
safe_pivotNo
target_fileYes
target_symbolNo
trigger_sourceNomanual_mcp
attempted_changeYes
error_root_causeYes
commit_or_run_refNo
dead_end_approachYes
raw_context_charsNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

With no annotations, the description must carry the full behavioral burden. It does disclose the transformation pipeline and a strict <=50 character alert constraint, but it never states persistence effects, permissions, idempotency, deduplication, or what happens when a dead end is recorded twice.

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?

The text is short and front-loaded: purpose first, then the extraction/encoding/alert pipeline. The unusual jargon is dense, but there is little obvious filler.

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

Completeness2/5

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

This is a complex, nine-parameter mutation tool with no annotations and no schema parameter descriptions, and the description leaves most inputs and all side-effect semantics unaddressed. The existence of an output schema covers return values, but not the invocation-critical 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 needs to define the nine inputs. It mentions only four fields (attempted_change, error_root_cause, dead_end_approach, safe_pivot) and leaves target_file, target_symbol, trigger_source, commit_or_run_ref, and raw_context_chars unexplained.

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?

It names a specific verb and resource ('Record a proven dead-end code change') and adds the expected artifacts, but the Anti-Memory/Scar Tissue and Memorilla-inspired phrasing is internal jargon. It also does not distinguish this tool from sibling check_scar_tissue.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance and no reference to check_scar_tissue as the alternative for querying scar tissue. The only implied condition is that the change must be a 'proven dead-end'.

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