Skip to main content
Glama

Change what one cast member is (and redraw just them)

describe_cast_member
Destructive

CHANGES ONE cast member into a different character: you pass a new one-line visual description, aicut rewrites the member's stored look from it and draws ONE new portrait (the rest of the roster is untouched). It is the tool for 'make the husband smaller and a white strawberry': NOT regenerate_cast_portrait (the SAME character again), nor a new generate_cast (it re-authors every member and re-buys every portrait). WHEN: the user wants a member to BE something else. character_id is the member's id from generate_cast_portraits or list_characters (kind cast_member); a free generate_cast draft has no library ids, so re-draft that instead. THE DESCRIPTION: ONE line of plain visual English, WHOLE, not a diff ('a small white strawberry man in a rumpled shirt', never 'the same but smaller'): the stored look is rebuilt from it alone, so fold in what the member already was; under about 500 characters. Do not read the line back: show the RESULT. IT PERSISTS: later episodes cast the NEW character. THE CARD: this call already put the aicut cast card up, each portrait filling in as it generates: do not poll or call show_generation (one get_image read of portrait_image_id if asked). No card (a terminal)? Poll each generating member's portrait_image_id with wait_for_generation (media image) and give the urls. AFTER: returns the member with its new description, portrait_image_id, portrait_status: "generating", changed (can be []) and a report: RELAY THE report as written. changed: [] means the member ALREADY had exactly this description and a portrait was bought anyway. IF THE PICTURE FAILS OR THE ACCOUNT RUNS OUT (402) THE DESCRIPTION HAS ALREADY CHANGED: the member is the new character wearing its old portrait; say so, and regenerate_cast_portrait draws the new look for one portrait's price. Do not re-send this tool (it buys a second picture). A 503 portrait_not_attached means the portrait WAS generated and CHARGED but did not attach: call THIS tool again with the quoted idempotency_key and the same arguments to re-attach it; a different key, or regenerate_cast_portrait, would buy a second one. COST: one standard image at image_model (or the platform default portrait model), the same as regenerate_cast_portrait; estimate_only: true prices it without re-describing anything. THE GO: one change, one named member, one priced ask. SPENDS TOKENS: price with estimate_only: true, ask in the SAME message as the price, and wait for a go that names THIS purchase (SPENDING RULES, this server's instructions). IDEMPOTENCY: a reused idempotency_key REPLAYS the first job whatever the settings: never reuse one for a new generation (this server's instructions).

Input Schema

NameRequiredDescriptionDefault
descriptionYesWhat this character looks like NOW: one whole line of plain visual English (see THE DESCRIPTION). Not a diff or an image prompt: anything omitted is lost.
image_modelNoImage model: the member's OWN `image_model` from `generate_cast_portraits` (matches the cast and its price). Omitted, the platform default portrait model is used: maybe a different look and price.
character_idYesThe cast member's library id: `id` on a `generate_cast_portraits` member or on a `list_characters` entry of kind `cast_member`.
estimate_onlyNoPrice only; creates nothing.
idempotency_keyNoRetry-safety key (IDEMPOTENCY).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Goes far past annotations: it discloses persistence into later episodes, the already-shown cast card and explicit no-polling rule, the `changed: []` meaning, the 402 case ('description already changed, old portrait'), and the 503 re-attach procedure with key semantics. Annotations only say destructive/openWorld; the description supplies the operational consequences.

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?

Dense but front-loaded: purpose first, then WHEN, then constraints, then cost/idempotency. Some material (COST, GO, IDEMPOTENCY) restates server-wide spending rules, which is mildly redundant, but every block addresses a real failure mode.

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

Completeness5/5

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

With no output schema, the description must carry the return contract, and it does: new `description`, `portrait_image_id`, `portrait_status: "generating"`, `changed`, and the `report` relay instruction. Failure modes, cost, and idempotency are all covered for a destructive, paid mutation.

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 coverage is 100%, so the baseline is 3, but the description genuinely adds: the description parameter must be a whole standalone line (not a diff), ~500 char limit, and `estimate_only` prices without re-describing. `idempotency_key` replay behavior is also explained beyond the schema's terse note.

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 ('CHANGES ONE cast member into a different character') with a capsule of the mechanism (rewrites stored look, draws ONE portrait, roster untouched). It explicitly contrasts with `regenerate_cast_portrait` and `generate_cast`, so an agent can route correctly without opening schemas.

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

Usage Guidelines5/5

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

The 'WHEN' clause names the selecting intent ('the user wants a member to BE something else') and both wrong alternatives with their reasons. It also covers the free-draft edge case (no library ids, re-draft instead) and the pre-spend 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.

Directories

Listed in ChatGPT · aicut

Last observed