Skip to main content
Glama

Read an existing Character Builder quote and recipe

get_character_builder_quote
Read-onlyIdempotent

Read the immutable Character Builder recipe, exact amount, expiry and state using its quoteId in the same account and OAuth client. This does not renew, reprice or approve the quote. Use get_character_builder_status to recover an existing submission.

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_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
quoteIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so the bar is lower, but the description adds real context: the recipe is immutable, and reads are scoped to the same account and OAuth client, which is an authorization constraint not present in structured data. It stops short of stating behavior for a missing, expired or foreign quoteId, which would complete the picture for a lookup keyed by an external identifier.

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?

Two compact sentences, front-loaded with the verb and the returned fields, followed by the constraint and the routing. No restatement of the tool name or filler wording.

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 single-parameter read-only tool with no output schema, the description covers purpose, returned fields, immutability, auth scoping, and explicit non-effects. Only error/not-found handling for the quoteId is unaddressed, which is a modest omission rather than a blocker.

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 0% (only a UUID regex, no prose), so the description carries the burden and does add meaning: quoteId must resolve within the same account and OAuth client, implying cross-client IDs will fail. It does not state the failure behavior or whether an expired quote still returns readable state, which is the main remaining gap.

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?

Specific verb ('Read') plus resource ('immutable Character Builder recipe') and an enumeration of what comes back: exact amount, expiry, state. It is distinguishable from get_recast_quote and from the prepare/confirm siblings without opening any 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?

Explicit when-not clause ('does not renew, reprice or approve the quote') and an explicit routing instruction to get_character_builder_status for recovering an existing submission. The agent knows both the boundary of this tool and the alternative for the ambiguous case.

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.