Skip to main content
Glama

Confirm one exactly priced Character Builder image

confirm_character_builder
DestructiveIdempotent

Submit one paid Character Builder image only after explicit approval of the exact fresh quote and recipe. Send its quoteId, amountCents, USD currency and confirmed=true. Do not use confirm_generation for a Builder quote. After timeout or an ambiguous response, recover the same quote using get_character_builder_status. A failure, refund or reconnect does not authorize a replacement; any further attempt needs a fresh quote and new approval. Save a completed original only when requested using save_character with the returned saveSource jobId and imageUrl, not a temporary presentation URL.

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": {
      "quoteId": "<quoteId>",
      "confirmed": "<confirmed>",
      "amountCents": "<amountCents>",
      "currency": "<currency>"
    },
    "name": "confirm_character_builder"
  }
}

Input Schema

NameRequiredDescriptionDefault
quoteIdYes
currencyYes
confirmedYes
amountCentsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

The annotations declare destructiveHint=true, openWorldHint=true, and idempotentHint=true, but they do not explain what destruction means. The description adds the important constraints: a payment is committed; a failure, refund, or reconnect does not authorize a replacement attempt; and a follow-up save must use the returned saveSource jobId and imageUrl rather than a temporary presentation URL. These are exactly the behavioral facts an agent needs before invoking a destructive paid operation.

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 description is dense but front-loaded: the action and precondition come first, then the parameter contract, then recovery and save semantics. Every sentence adds a rule the agent needs, though the final save_character sentence is tangential to confirming and slightly lengthens the definition.

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?

The description covers the precondition, the payload contract, the timeout and recovery path, the retry prohibition after failure or refund, and the downstream save handoff. Nothing an agent needs in order to call a destructive, open-world paid confirmation correctly is missing, even without an output schema.

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 description coverage is 0%, so the description has to carry parameter meaning, and it does: quoteId, amountCents, and USD currency must come from the exact approved quote, and confirmed must be true after explicit approval. It does not explain the units or bounds of amountCents or the UUID format of quoteId, but those are evident from the schema's const and format fields.

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?

States a specific verb and resource ('Submit one paid Character Builder image') and pins the precondition ('only after explicit approval of the exact fresh quote and recipe'). It also explicitly separates itself from the sibling confirm_generation: 'Do not use confirm_generation for a Builder quote.'

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?

Names the prerequisite (fresh quote plus explicit approval of exact recipe and price), the excluded alternative (confirm_generation), and the recovery path after a timeout or ambiguous response (get_character_builder_status for the same quote). It also rules out retries after a failure, refund, or reconnect without a new quote and approval, so an agent has an explicit when-to-use and when-not-to-use rule set.

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.