CutClip.one

character.create

Add a recurring character to the cast. Describe appearance precisely — it drives the generated reference sheet.

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": {
      "projectId": "<projectId>",
      "expectedVersion": "<expectedVersion>",
      "name": "<name>"
    },
    "name": "character.create"
  }
}

Input Schema

Name	Required	Description
`name`	Yes
`role`	No
`notes`	No
`voiceId`	No	ElevenLabs voice this character speaks with (voice.list); null clears it
`wardrobe`	No
`projectId`	Yes
`voiceName`	No	The voice's display name, as voice.list gives it
`appearance`	No	Face, hair, build, age — identity details that must not drift
`description`	No
`expectedVersion`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 6, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full disclosure burden for a mutation tool, yet it says nothing about permissions, required project state, failure modes, or the meaning of the required expectedVersion parameter (optimistic concurrency is never mentioned). The only real behavioral fact offered is that appearance feeds the reference sheet, which is useful but far short of what a 10-parameter create operation needs.

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?

Two compact sentences, with the core action front-loaded and the appearance caveat second. Nothing is redundant, though the brevity comes partly from under-specification rather than tight editing.

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?

With 10 parameters, no annotations, no output schema, and unexplained concurrency/versioning semantics, the description leaves an agent without enough to call this correctly. It does not say what a successful call returns, what state the character is left in, or how to recover from a version conflict.

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

Parameters2/5

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

Schema description coverage is only 30% across 10 parameters, and the description clarifies just one of them: appearance, whose consequence (drives the generated reference sheet) genuinely extends the schema's wording. Required parameters like projectId and expectedVersion, plus role, notes, wardrobe, voiceName, and description, receive no explanation anywhere.

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?

"Add a recurring character to the cast" states a specific verb (add) and resource (character) with scope (recurring, cast). It is distinguishable from character.update by the word "add," though the description never names any 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?

There is no explicit when-to-use or when-not-to-use guidance versus character.update or character.add_reference. The one implied usage hint is that a precise appearance description matters because it drives the generated reference sheet, which indirectly signals a prerequisite relationship with character.generate_sheet.

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

All CutClip.one tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.