claude-engram

by 20alexl

Overview Schema Source Related Servers Discussions Admin

Python

Local

pre_edit_check

Prevent editing errors by checking past mistakes, loop risks, and scope violations before modifying a file.

Instructions

Run BEFORE editing important files. Checks: past mistakes, loop risk, scope violations.

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": {
      "file_path": "<file_path>"
    },
    "name": "pre_edit_check"
  }
}

Input Schema

Name	Required	Description	Default
`file_path`	Yes	File about to edit

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Apr 26, 2026

TDQS

B3.4/5.0

Behavior2/5

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

No annotations provided; description does not disclose side effects, authorization needs, rate limits, or return behavior. Only lists what it checks, which is minimal transparency.

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 wasted words, key information front-loaded. Highly concise and well-structured.

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?

Missing output schema and description does not specify return value or format. For a check tool, agents need to know what to expect (e.g., boolean, list, or summary) for decision-making.

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 coverage is 100% with a clear description for 'file_path.' The tool description adds no additional meaning beyond what the schema already provides, so baseline 3 applies.

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?

Description clearly states it is a pre-edit check tool that examines past mistakes, loop risk, and scope violations, distinguishing it from sibling tools like code_pattern_check or code_quality_check.

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?

Explicitly says 'Run BEFORE editing important files,' providing clear timing for use. Does not specify exclusions or alternatives, but context is strong.

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