Skip to main content
Glama

Redraw a lookbook piece

redraw_music_video_lookbook_piece

Draws one of the director's pieces again, with an optional note (spends credits) credits: price.credits_per_picture.

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": {
      "lookbook_id": "<lookbook_id>",
      "piece": "<piece>",
      "credits": "<credits>"
    },
    "name": "redraw_music_video_lookbook_piece"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNoWhat to change: "warmer light, nobody else"
pieceYesThe piece's number
creditsYesThe price shown (price.credits_per_picture)
lookbook_idYesThe lookbook id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare openWorldHint=true, idempotentHint=false, destructiveHint=false; the description adds the important behavioral fact that this consumes credits. It still omits whether the redraw replaces the existing piece or produces an additional variant, and how many credits a single redraw costs.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single short sentence, which is appropriately front-loaded, but the trailing 'credits: price.credits_per_picture' fragment is malformed and repeats schema content rather than adding information.

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?

For a credit-spending, non-idempotent generation tool with no output schema, the definition should say what the agent gets back (a new piece? a status?), whether the prior piece is kept, and how to read the price before calling. None of that is present, leaving gaps an agent must guess at.

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?

Schema coverage is 100% and all four parameters are described in the schema, so baseline 3 applies. The description notes the note is optional and ties credits to price.credits_per_picture, but the latter is garbled phrasing that adds little beyond the schema's own description.

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?

'Draws ... again' is a specific verb applied to a specific resource, and the optional-note/edit framing makes the operation recognizable. The phrasing 'one of the director's pieces' is looser than the tool name's 'lookbook piece', so the link to the lookbook resource is inferred rather than stated.

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 on when to redraw versus redesign_music_video_lookbook, keep_music_video_lookbook_piece, or render_music_video_lookbook, all of which sit adjacent. The only selection signal is that it spends credits, which is a caveat, not a routing rule.

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