Skip to main content
Glama

Quote failed generation items

playground_media_retry_quote
Read-only

Read fresh receipts for one run and quote replacements only for confirmed failed items, including individual List outputs. Completed, pending, active, uncertain and changed-reference items are excluded. Optional dispatchIds selects failed items explicitly. Quote only: no canvas edit, approval or generation. Returns exact retryPlan.items and quoteId for playground_media_generate; user confirmation is still required before spending.

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>",
      "runId": "<runId>"
    },
    "name": "playground_media_retry_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
runIdYesRun ID returned by preparation or execution for this project.
projectIdYesID of the Playground project chosen for this task; obtain it from project creation, an explicit project link or current context.
dispatchIdsNoDispatch receipt IDs for the failed items to retry; obtain them from run_delivery recovery.

Output Schema

NameRequiredDescriptionDefault
nextNoSuggested next action; it does not authorize spending.
itemsNo
runIdNo
reviewNo
statusYes
balanceNo
quoteIdNo
recoveryNo
revisionNo
canvasUrlNo
expiresAtNoSerialized ISO timestamp.
projectIdNo
retryPlanNo
totalCreditsNo
validitySecondsNo
inputFingerprintNo
sufficientCreditsNo
estimatedBalanceAfterNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Beyond readOnlyHint/destructiveHint=false it discloses concrete behavior the annotations cannot convey: receipts are re-read fresh, only confirmed failures are quotable, no canvas edit/approval/generation occurs, spending requires separate user confirmation, and the response carries exact retryPlan.items and quoteId for playground_media_generate. This is materially useful safety and workflow context for a non-destructive but money-adjacent operation.

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?

Four dense sentences, front-loaded with the core action and scope, followed by exclusions, the guardrail, and the handoff to the next tool. No redundant restatement of the title or schema; every clause carries information.

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?

Complete for a read-only quoting tool: inputs, exclusions, side-effect boundaries, confirmation requirement and the downstream consumer of quoteId are all covered, and an output schema exists so return structure needs no further explanation. Nothing an agent needs in order to call it and act on the result is missing.

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 description coverage is 100%, so runId, projectId and dispatchIds are already documented in the schema. The description adds only a modest clarification that dispatchIds explicitly selects failed items; it does not explain the 20-item cap, ordering, or what happens when omitted. Baseline 3 is appropriate.

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?

States a concrete verb+resource pair: reads fresh receipts for one run and quotes replacements for confirmed failed items, explicitly including individual List outputs. Scope is bounded by naming the excluded item states (completed, pending, active, uncertain, changed-reference). It does not distinguish itself from same-family quote tools such as playground_image_quote or playground_video_quote, so sibling differentiation is only partial.

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?

Explicitly enumerates what is excluded (completed, pending, active, uncertain, changed-reference items) and describes the optional dispatchIds path for selecting failed items explicitly. It also carves out the boundary of the operation: 'Quote only: no canvas edit, approval or generation,' and notes that user confirmation is still required before spending. An agent knows both when to call it and what it must do afterwards.

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.