Skip to main content
Glama

Confirm a quoted generation charge

playground_approval_decide
Destructive

After showing the exact prompts, references and total credits in chat and receiving the user’s explicit confirmation, approve or reject one direct generation request created by this client. Approval submits a paid job. Pass its inputFingerprint and maxCredits from the prepared request. Never call approve before the user confirms. Cannot approve another client’s requests or delegated agent plans. Returns the approval decision result, including dispatch or rejection status.

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>",
      "approvalId": "<approvalId>",
      "decision": "<decision>",
      "inputFingerprint": "<inputFingerprint>",
      "maxCredits": "<maxCredits>"
    },
    "name": "playground_approval_decide"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.
approvalIdYesApproval ID from the prepared request or approvals_list.
maxCreditsYesMaximum credits explicitly approved by the user; copy the quoted ceiling without increasing it.
inputFingerprintYesExact input fingerprint from the quote, binding approval to the reviewed inputs.

Output Schema

NameRequiredDescriptionDefault
errorNo
jobIdNo
nodeIdNo
statusYes
receiptNo
dispatchesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and openWorldHint=true, but the description adds the crucial consequence the annotations cannot express: approving submits a paid job that consumes credits. It also states the return shape at a high level (dispatch or rejection status) and the client-scoping restriction. It does not spell out irreversibility or what happens to a rejected request beyond a status, which keeps it short of a 5.

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 confirmation precondition is front-loaded and every sentence carries safety or scoping information. There is mild redundancy between the opening clause about receiving the user's explicit confirmation and the later 'Never call approve before the user confirms,' which repeats the same rule in stronger form.

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?

For a destructive, credit-consuming approval tool with five required parameters, the description covers the precondition, the cost consequence, the scope limits and the result. An output schema exists and the description still summarizes the return, so nothing an agent needs before invoking it 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 100%, so the baseline is 3; the description earns a bump by telling the agent where inputFingerprint and maxCredits come from ('from the prepared request') and framing them as the binding constraint on the charge. It says nothing about projectId or approvalId beyond what the schema already documents.

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?

The description names a specific verb pair (approve or reject) and a precisely scoped resource: one direct generation request created by this client. It also excludes neighboring cases (another client's requests, delegated agent plans), so an agent can tell this apart from the sibling approval and generation tools without opening a schema.

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?

It states the required precondition explicitly ('after showing the exact prompts, references and total credits in chat and receiving the user's explicit confirmation') and adds a hard prohibition ('Never call approve before the user confirms'). The alternative path for delegated agent plans and other clients is named as out of scope, and approvals_list is referenced as the source of approvalId.

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.