Skip to main content
Glama

Recover a Character Builder image by quote

get_character_builder_status
Read-onlyIdempotent

Recover the existing Character Builder job using its original quoteId after timeout, disconnect or ambiguous confirmation. Account and OAuth client scope remain enforced when execution closes. Follow retry.afterSeconds and stop automatic polling when retry is null. Deliver only completed image results. To save on request, pass saveSource.jobId and saveSource.imageUrl to save_character; presentation URLs are temporary. A missing job, failure or refund never authorizes a replacement.

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

Input Schema

NameRequiredDescriptionDefault
quoteIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds substantial context beyond them: account and OAuth client scope are still enforced, retry.afterSeconds governs polling and null retry means stop, only completed image results are delivered, and presentation URLs are temporary. It also sets an important expectation that a missing job, failure, or refund does not authorize a replacement, which prevents an agent from taking a wrong follow-up action.

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?

Every sentence carries actionable content and the recovery scenario is front-loaded before polling rules and the save handoff. It is dense but not padded; the only cost is that polling/save/refund guidance are packed into one flat block without visual separation, making it slightly harder to scan.

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 single-parameter, read-only retrieval tool with no output schema, the description covers purpose, trigger conditions, polling behavior, what is returned (completed images only), URL transience, and failure semantics. Nothing an agent needs in order to call it correctly or interpret 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?

There is a single parameter with 0% schema description coverage, so the description must carry the meaning. It adds the key nuance that quoteId must be the ORIGINAL one, and mentions saveSource.jobId/imageUrl for the save_character handoff, but it does not say where the quoteId comes from or that it must match the initiating account. The schema's uuid format and version-4 pattern already convey the syntax.

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 states a specific verb+resource: recover an existing Character Builder job keyed by its original quoteId. It distinguishes itself from the prepare/confirm/quote siblings by framing the tool around post-timeout recovery rather than initiating work. The only softness is the framing mismatch with the name 'get_..._status' — 'recover' could momentarily suggest a mutation, though the rest of the text clarifies it is a retrieval.

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 names the precise triggering conditions: after timeout, disconnect, or ambiguous confirmation. It also gives forward guidance by naming save_character with the saveSource.jobId/saveSource.imageUrl handoff. It stops short of explicitly saying when not to use this (e.g. use prepare_character_builder to start a job), but the recover-after-failure framing implicitly routes the agent.

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.