Skip to main content
Glama

order_quote

Get fresh quotes for the order as it stands (e.g. after quotes expired).

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": {
      "order": "<order>"
    },
    "name": "order_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
orderYesOrder id (ord_…).

Output Schema

NameRequiredDescriptionDefault
okYes
dataNo
errorNo
summaryNo
warningsNo
next_actionsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

The annotations already disclose readOnlyHint=false, idempotentHint=false and destructiveHint=false, so the safety profile is covered externally. The description adds the useful context that quotes expire, but it leaves the non-idempotent behavior unexplained—an agent cannot tell from the text that each call likely produces new quotes with side effects, or what happens to previously issued quotes.

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?

One short sentence with the trigger front-loaded in a parenthetical; there is no filler. The trade-off is that the brevity leaves behavioral gaps, but structurally the description is tight and front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be explained, and annotations cover the safety profile. For a non-idempotent, open-world call with side effects on an order, the description should still say what 'fresh' means and what happens to existing quotes, so it is adequate but not complete.

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?

The schema documents the single `order` parameter at 100% coverage (order id, ord_… prefix), so the parameter is fully explained without the description. The description adds only the mild nuance that the order is taken "as it stands", which is consistent with the schema rather than adding new meaning.

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 verb and resource are specific: "Get fresh quotes for the order." The parenthetical "as it stands (e.g. after quotes expired)" clarifies the trigger, but the description never says whether fresh quotes are generated server-side or merely re-fetched, leaving a small ambiguity about what the tool actually does to an order versus sibling tools like order_show.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase "as it stands (e.g. after quotes expired)" gives one concrete usage trigger, which is more than nothing. However, it never excludes use cases, never points to order_show vs order_purchase vs order_wait, and gives no guidance on how often to request fresh quotes or what to do with previously fetched quotes.

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.

Resources