Skip to main content
Glama

x420_quote

Read-only

Get a free price quote for one agent service by providing amount, currency, rail, pay-to address, nonce, and expiry; no order is placed.

Instructions

Free. Asks X420 for a price quote (POST https://signature-theme.com/a2a/quote) for one service and input: amount in USD, currency, rail, pay-to address, nonce and expiry. A quote costs nothing and does not place an order.

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": {
      "service": "<service>"
    },
    "name": "x420_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
railNopayment rail; default x402
inputNothe service's input parameters (string values), exactly as you would pass to its tool
serviceYesservice id from the catalog, e.g. sitescan.check

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, and the description reinforces them by stating the quote is free and places no order — exactly the side-effect assurance an agent needs for a POST-shaped call. It stops short of saying whether quotes are binding, how long they last, or what the response contains.

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?

Two tight sentences with the most decision-relevant fact ('Free') front-loaded, and the no-order guarantee stated early. The endpoint URL is arguably filler but is short enough not to hurt.

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?

There is no output schema, so the description carries the burden of explaining what a quote returns — price, expiry, payment target — and it does not. It does cover inputs and side effects well, leaving a meaningful gap for a tool whose whole purpose is producing a priced response.

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 baseline is 3, but the description earns more by enumerating what belongs inside the nested `input` object (amount in USD, currency, rail, pay-to address, nonce, expiry) — content the top-level schema only describes generically as 'the service's input parameters'.

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?

States a specific verb and resource ('Asks X420 for a price quote') plus the exact scope ('for one service and input') and even the underlying endpoint. An agent can distinguish this from the catalog lookup or the actual service tools 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 Guidelines3/5

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

The phrase 'does not place an order' implies this is a pre-purchase price check, which is useful implicit guidance. However, it never explicitly says when to call this instead of invoking the service tool directly, nor does it name any alternative, so the routing decision 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.