Skip to main content
Glama
Sign In
Claude-Code MCP Runner

Claude-Code MCP Runner

by DeamonDev888
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

edit_prompt

Edit an existing prompt by replacing a specific text block with new content. Modify agent instructions or configurations directly.

Instructions

Modifie un prompt existant en remplaçant un bloc de texte spécifique

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": {
      "name": "<name>",
      "search": "<search>",
      "replace": "<replace>"
    },
    "name": "edit_prompt"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesNom du fichier prompt à modifier (ex: 'agent_news')
searchYesLe texte exact à rechercher et remplacer
replaceYesLe nouveau texte de remplacement

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.8/5.0
Behavior2/5

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

No annotations provided; description only says 'replaces a specific text block' but does not disclose side effects, whether it modifies the file in place, or if the operation is reversible. Insufficient for a mutation tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence is concise but lacks detail. Could include usage notes or examples without being verbose.

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?

Description is too brief for a tool with 3 required parameters. It doesn't specify behavior like exact match replacement, case sensitivity, or return value. Incomplete for effective use.

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 clear parameter descriptions. The tool description adds no additional meaning beyond the schema, meeting baseline.

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 the verb 'modifie' (modify) and resource 'prompt existant' with specific action 'remplaçant un bloc de texte spécifique'. It distinguishes from sibling 'create_prompt' which is for creating new prompts.

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?

No explicit guidance on when to use this tool vs alternatives. Lacks context about prerequisites or scenarios where editing is preferred over creating a new prompt.

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