Skip to main content
Glama

Redraw a cover

redraw_cover

Draws one cover of a round again with the user’s note Keeps the idea and changes what the note asks ("warmer, the moon bigger"). A new round of one cover; the cover it came from stays on the song. credits: redraw_credits from quote_cover, as shown to the user. Needs a paid plan.

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": {
      "request_id": "<request_id>",
      "cover_id": "<cover_id>",
      "note": "<note>",
      "credits": "<credits>"
    },
    "name": "redraw_cover"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteYesWhat to change, in the user's words
creditsYesredraw_credits from quote_cover
cover_idYesThe cover to redraw (cover_…)
request_idYesThe round the cover came from (coverreq_…)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already flag a non-read-only, non-idempotent, non-destructive, open-world mutation. The description adds real value beyond that: each call starts 'a new round of one cover', the original cover stays attached to the song, credits are consumed and must be quoted first, and a paid plan is needed. What it doesn't disclose is failure behavior or what happens to the prior round's artifacts.

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?

The whole definition is three short clauses with no filler and the core action is front-loaded. It loses a point for run-on punctuation ('with the user's note Keeps the idea') that slightly obscures where one claim ends and another begins.

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

Completeness3/5

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

For a paid, credit-consuming mutation the description covers cost, plan gating, and source-preservation, which is good. However, with no output schema, the agent is never told what a successful redraw returns (a new cover id, a request id, a job status), leaving a meaningful gap for a multi-step flow.

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%, with each of the four parameters already documented including formats (cover_…, coverreq_…). The description reinforces the intent of note ('keeps the idea, changes what the note asks') and the origin of credits, but adds little beyond the schema's own text, so the baseline 3 applies.

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?

The description names a specific verb and resource ('Draws one cover of a round again') and clarifies how the result differs from the source ('the cover it came from stays on the song'). It does not explicitly name the neighboring tools like make_cover or use_cover, so the agent must infer the boundary from phrasing alone.

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?

It gives a clear trigger ('with the user's note', 'changes what the note asks') and a prerequisite chain: credits come from quote_cover and a paid plan is required. It stops short of stating when to choose make_cover or use_cover instead, so the alternative-selection guidance is incomplete.

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