Skip to main content
Glama

quote_capability

Validate inputs and obtain a five-minute quote bound to your buyer identity, exact input, capability version and price. Does not reserve credits.

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": {
      "capability_id": "<capability_id>",
      "input": "<input>"
    },
    "name": "quote_capability"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYesInput satisfying capability input_schema
capability_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, idempotentHint=false, destructiveHint=false, openWorldHint=true), the description discloses concrete behavior: the quote has a five-minute lifetime, is bound to buyer identity, exact input and capability version, and crucially does not reserve credits. That last clause resolves the ambiguity of a non-read-only tool that still has no side effects on credits.

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 tight sentences with the core behavior and its scope stated first, followed by the important exclusion. No filler or redundancy.

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 two-parameter tool with no output schema, the description covers what is produced (a quote) and its key attributes (price, version, expiry, binding). It stops short of describing the shape of the returned quote (e.g., identifier or field list), which matters without an output schema, but the essentials for correct invocation are present.

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?

With two parameters and 50% schema description coverage, capability_id is undocumented in the schema. The description adds only that the input is used 'exactly' as supplied and is validated against the capability's input schema, but it gives no format guidance for capability_id, so the schema description gap is only partially compensated.

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 specific verb-plus-resource: it validates inputs and returns a five-minute quote bound to buyer identity, input, capability version and price. That is clearly distinct from order creation in the sibling list, and 'Does not reserve credits' further separates it from create_order, though no sibling is named explicitly.

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?

Usage is implied rather than stated: the phrase 'Does not reserve credits' hints that a separate step is needed to actually commit, which nudges the agent toward create_order. However, there is no explicit 'use this before X' or 'do not use this when Y' guidance, so the agent must infer the placement of this call in the workflow.

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