Skip to main content
Glama

Quote a paid call

quote
Read-onlyIdempotent

Returns the exact price_credits for one paid call (for_tool + its args) and a quote_id valid 5 minutes and once; pass it to that tool. For bots_call it also returns free_left_today. Free (charges nothing). Needs sign-in (auth_challenge then auth_verify).

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": {
      "for_tool": "<for_tool>"
    },
    "name": "quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
argsNoThat tool's arguments as an object (or pass them at the top level)
for_toolYesThe paid tool to price: ai_chat, image_generate, audio_transcribe or bots_call

Output Schema

NameRequiredDescriptionDefault
blockNo
staleNo
sourceNo
quote_idNo
price_creditsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / args / description
      Previous value: -"That tool's args (or pass them at the top level)"New value: +"That tool's arguments as an object (or pass them at the top level)"
    • changedInput schema / properties / for_tool / description
      Previous value: -"The paid tool to price"New value: +"The paid tool to price: ai_chat, image_generate, audio_transcribe or bots_call"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": true,
      +  "properties": {
      +    "block": {
      +      "type": [
      +        "integer",
      +        "null"
      +      ]
      +    },
      +    "price_credits": {
      +      "type": "integer"
      +    },
      +    "quote_id": {
      +      "type": "string"
      +    },
      +    "source": {
      +      "type": "string"
      +    },
      +    "stale": {
      +      "type": "boolean"
      +    }
      +  },
      +  "type": "object"
      +}
  2. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing cost ('charges nothing'), quote lifetime (5 minutes), single-use semantics, the required auth sequence, and the extra free_left_today field for bots_call. These are exactly the behavioral facts an agent cannot derive from readOnlyHint/idempotentHint alone. The 'valid once' note is a useful caveat about the token rather than a contradiction of idempotentHint, since the call itself is a free read.

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?

A single dense paragraph with no wasted words: return values first, then validity constraint, then the action to take, then cost and auth prerequisites. Every clause carries information an agent needs.

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?

With an output schema present, the description need not detail response shape, and it correctly focuses on cost, TTL, single-use, auth flow, and how to consume the quote_id. Nothing needed to call this two-parameter tool correctly is missing.

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 100%, so the baseline is 3, but the description adds meaning by clarifying that args are the target tool's arguments and that they may be passed at top level, and that for_tool selects among four specific paid tools. It also ties the quote to the exact call configuration, which helps the agent understand why args matter.

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?

States a concrete verb and resource: returns price_credits and a quote_id for one paid call, parameterized by for_tool plus its args, and names the four priceable tools. An agent knows exactly what it gets back. The one gap is that it does not distinguish itself from near-siblings like price_list or get_credits_quote, which appear to offer related pricing information.

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?

Gives clear operating context: it is free, requires sign-in via auth_challenge then auth_verify, and the returned quote_id must be passed to the priced tool. It does not state when to prefer this over price_list or get_credits_quote, so routing between pricing tools is left to inference.

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