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

Claude-Code MCP Runner

by DeamonDev888
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

create_prompt

Creates or overwrites a Markdown prompt file to define a persona for Claude Code agents. Use it to configure agent personalities and mission instructions.

Instructions

Crée ou écrase un fichier prompt Markdown (Persona)

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>",
      "content": "<content>"
    },
    "name": "create_prompt"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesNom du fichier prompt (sans extension). Ex: 'analyse_financiere'
contentYesContenu Markdown du prompt

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior4/5

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

The description explicitly mentions the overwrite behavior ('écrase'), which is a destructive action. Since no annotations are provided, this disclosure is important for an agent to understand the potential side effect.

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 description is a single concise sentence that is front-loaded with the action and resource. It avoids unnecessary words.

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?

The description lacks context about when to use the tool, success indications, error conditions, or how it differs from edit_prompt. For a tool with no output schema and no annotations, this is insufficient for an agent to fully understand its behavior.

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?

The input schema provides full descriptions for both parameters (name and content), achieving 100% coverage. The tool description adds no additional parameter-specific meaning beyond the schema, so a score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool creates or overwrites a prompt Markdown file (Persona), using the verb 'crée ou écrase' and specifying the resource. This distinguishes it from siblings like create_agent or edit_prompt.

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 guidance is provided on when to use this tool versus alternatives, such as edit_prompt. The description does not mention prerequisites or situations where overwriting is appropriate.

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