Skip to main content
Glama

create_character_video_order

Create an UNPAID order for 1–2 original characters, without photos. ONLY call after the user explicitly approves the characters, four lyrics and delivery email. No charge, Stripe session or video generation happens here. One video $6.99; three $15.99, one-time purchase. Give payUrl exactly as returned; the user must open it and pay personally. Do not automatically retry an uncertain order call.

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": {
      "characters": "<characters>",
      "topic": "<topic>",
      "lines": "<lines>",
      "stage": "<stage>",
      "offer": "<offer>",
      "email": "<email>"
    },
    "name": "create_character_video_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailYes
linesYes
offerYes
stageYes
topicYes
charactersYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint=false, idempotentHint=false, openWorldHint=true), it discloses consequential behavior: no charge or Stripe session occurs, payUrl must be returned verbatim, and the user must pay personally. The no-auto-retry warning directly addresses the non-idempotent write risk that the annotation only flags abstractly.

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?

Roughly six short sentences, each carrying a distinct constraint, with the most important facts (unpaid, precondition, no side effects) front-loaded. No filler or repetition.

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?

For a six-required-parameter mutation with no output schema, the description covers the critical output (payUrl) and the payment handoff, which is what an agent most needs. Gaps remain on stage/topic meaning and on the next step after payment (get_order_status), but the core call path is adequately specified.

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?

With schema description coverage at 0%, the description carries the full burden; it clarifies characters (1–2, original, no photos), the exactly-four 'lines' array, the delivery email, and maps offer pricing to single vs three. However, 'stage' and 'topic' are never explained, leaving the five-value stage enum and topic length/format entirely undocumented anywhere.

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 ('Create an UNPAID order for 1–2 original characters') and scopes it with 'without photos', which separates it from the photo-video path implied by get_photo_video_link. The 'UNPAID' qualifier and 'No charge, Stripe session or video generation happens here' make the tool's actual effect unmistakable.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit gating precondition: only call after the user approves the characters, four lyrics and delivery email, and adds a 'do not automatically retry' rule for uncertain calls. It stops short of naming siblings (e.g., draft_lyrics for the lyrics step, get_order_status after payment), so the agent must infer the surrounding workflow.

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