Skip to main content
Glama

Ask for a new quote

request_new_quote

For an order token whose quote has expired: a fresh 20-minute quote, and the order's status read again.

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_token": "<order_token>"
    },
    "name": "request_new_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
order_tokenYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false), so the description is not carrying the full burden. It still adds real behavioral detail beyond them: the new quote is valid for 20 minutes, and the call also re-reads order status, which explains why a non-readOnly refresh is useful. It does not say whether the expired quote is invalidated or what happens if the current quote is still valid.

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 sentence with no filler, and the precondition is front-loaded before the effects. The fragmentary grammar and the trailing comma clause make it slightly less crisp than it could be, but nothing is wasted.

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 tool with no output schema and full annotation coverage, the description covers the trigger, the outcome mutation, and the 20-minute validity window. The remaining gap — behavior when the quote has not expired — is minor for a tool this simple.

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%, so the description must supply meaning for order_token, and it does: the token must belong to an order whose quote has already expired, which is a state constraint absent from the schema. It stops short of describing the token format or the failure mode when the precondition is not met.

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 names a specific action (issuing a fresh quote) and its precondition (an order token whose quote has expired), plus a secondary effect (order status read again). That is more than a restatement of the name, though the elliptical, fragment-like phrasing ('a fresh 20-minute quote, and the order's status read again') makes the agent work slightly to parse the verb.

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?

The precondition 'For an order token whose quote has expired' is an explicit trigger that tells the agent when this tool applies rather than get_order_status. No when-not guidance or named alternatives are given, so it falls short of 5, but the context is unambiguous.

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