Skip to main content
Glama

Confirm generation batch

playground_generation_confirm
Destructive

After explicit user confirmation of exact inputs and total credits, submit all selected direct-generation approvals from one run in one call. Pass confirmation.items and totalCredits from the prepared request as items and maxCredits. Validates all client/user/run bindings before dispatch; preserves already-submitted items on retries and reports every partial failure. Never call before user confirmation. No Berrys review-page click is needed.

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>",
      "decision": "<decision>",
      "maxCredits": "<maxCredits>",
      "items": "<items>"
    },
    "name": "playground_generation_confirm"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsYes
runIdYesRun ID returned by preparation or execution for this project.
decisionYesWhether to approve or reject the selected proposal; approve charges only after explicit user confirmation.
projectIdYesID of the Playground project chosen for this task; obtain it from project creation, an explicit project link or current context.
maxCreditsYesSum of the quoted credit ceilings for all selected items, explicitly confirmed by the user.

Output Schema

NameRequiredDescriptionDefault
nextYesSuggested next action; it does not authorize spending.
itemsYes
runIdYes
statusYes
projectIdYes
dispatchesYes
confirmedCreditsYes
unresolvedApprovalIdsYes
alreadySubmittedCreditsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Goes beyond the annotations (destructiveHint=true, openWorldHint=true, idempotentHint=false) by disclosing that client/user/run bindings are validated before dispatch, that already-submitted items survive retries, and that partial failures are reported per item. This is exactly the kind of consequence-and-retry detail an agent needs for a credit-charging mutation; it just doesn't state what a full failure leaves behind.

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?

Four dense sentences with the confirmation precondition front-loaded and each sentence carrying distinct information (mapping, validation, retry, prohibition). Slightly packed but no wasted clauses.

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 5-parameter destructive confirmation tool with an output schema and rich annotations, the description covers prerequisites, value sourcing, validation ordering, and retry semantics. Return-value detail is legitimately left to the output schema, so nothing critical is missing.

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 80%, so baseline would be 3, but the description adds genuine cross-field mapping: copy confirmation.items and totalCredits from the prepared request into items and maxCredits. That tells the agent where the values originate, which the schema alone does not.

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 specific verb and resource: submit all selected direct-generation approvals from one run in a single call. The batch scope ('in one call') implicitly separates it from the single-item playground_approval_decide, though no sibling is named outright.

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 a clear precondition ('After explicit user confirmation of exact inputs and total credits') plus a hard prohibition ('Never call before user confirmation') and a note that no Berrys review-page click is needed. It stops short of explicitly routing to alternatives such as playground_approval_decide for single-item decisions.

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.