Skip to main content
Glama

Edit file

edit_file
Destructive

Exact string replace in a file (fails if old_string is not unique)

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": {
      "path": "<path>",
      "old_string": "<old_string>",
      "new_string": "<new_string>"
    },
    "name": "edit_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
new_stringYes
old_stringYes
project_idNoProject id (or use session from use_project)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=false, so the safety profile is covered. The description adds genuine value by disclosing the uniqueness failure mode, but it omits other relevant behavior: what happens when old_string is absent, whether the write is atomic, and how it interacts with project_id scoping.

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?

One front-loaded sentence with zero filler, and the failure condition is attached directly to the operation it qualifies. It is efficient, though the terseness leaves the reader with open questions rather than fully resolving the operation.

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?

For a destructive 4-parameter mutation tool with no output schema, the description covers the signature failure mode but leaves the agent without guidance on non-unique-match recovery, missing-match behavior, or how project_id/session scoping affects the target file.

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 low at 25% — only project_id is documented in the schema. The description compensates partially by naming old_string and explaining its uniqueness requirement, but path and new_string receive no explanation of format or semantics in either place.

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?

States a specific operation and resource: "Exact string replace in a file", with the parenthetical clarifying the semantics of the match. An agent can distinguish this from write_file or read_file by the exact-match replacement framing, though it never names a sibling explicitly.

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 uniqueness constraint implies this is for targeted, single-occurrence edits rather than whole-file rewrites, which is indirect guidance toward edit_file over write_file. However, there is no explicit statement of when to prefer this tool versus alternatives, and no prerequisites or preconditions are called out.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources