Skip to main content
Glama

Save Character Prompt

save_character_prompt
Destructive

[write] Save a prompt for the caller's studio list kind (looks | outfits | poses | locations | profiles), up to 4000 characters; the same text twice is kept once. Answers characters_prompt_uuid.

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": {
      "kind": "<kind>",
      "text": "<text>"
    },
    "name": "save_character_prompt"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYes
textYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare the write/destructive profile, so the description's added context is what earns credit: a hard 4000-character cap, deduplication semantics ("the same text twice is kept once"), and the returned field `characters_prompt_uuid`. It still does not explain what the destructiveHint=true implies (e.g., whether saving replaces an existing prompt for that kind), which is the one gap for a destructive mutation.

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?

A single compact sentence, front-loaded with the mutation marker and the resource, with all extra detail (enum values, length cap, dedup, return field) packed into semicolon-separated clauses. No filler.

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

Completeness4/5

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

Covers both parameters, the size limit, dedup behavior, output field name, and the fact that prompts live on the caller's studio list rather than being character-scoped — enough to call it correctly without an output schema. The remaining ambiguity about replacement/overwrite behavior on re-save for an existing kind is minor but real for a destructive tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry both parameters — and it does: it enumerates the valid `kind` values (looks | outfits | poses | locations | profiles) and constrains `text` to 4000 characters. It does not state whether `kind` is strictly closed-enum or free-form, which keeps this just short of full coverage.

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?

States a specific verb and resource ("Save a prompt") plus the scope ("the caller's studio list `kind`"), and enumerates the five kinds so the agent knows exactly what object is being written. It is clearly distinguishable from siblings such as list_character_prompts and delete_character_prompt.

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 leading "[write]" tag signals this is the mutation counterpart to the list/delete prompt tools, which implies when to reach for it. However, it never explicitly says when to use this versus delete_character_prompt, list_character_prompts, or create_visibility_prompt, and gives no prerequisites or exclusions.

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.