Skip to main content
Glama

pons_quote

Converts a USD amount into USDG base units (6 decimals) and returns a settlement plan without executing the payment.

Instructions

Quote a payment: converts a USD amount into USDG base units (6 decimals) and returns the settlement plan without executing.

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": {
      "amountUsd": "<amountUsd>"
    },
    "name": "pons_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
amountUsdYesUSD amount, e.g. "5.00"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior4/5

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

No annotations exist, so the description must carry the safety profile — and it does: it explicitly declares the call is non-executing (read-only, no side effects) and pins the conversion format (USD to USDG base units, 6 decimals). It omits whether quotes expire or must be used within a window, which matters for a quote-then-pay flow.

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 front-loaded sentence that names the action, the conversion, the return value, and the non-execution constraint with zero filler.

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 one-parameter tool with no output schema, the description covers the key contract: input is USD, output is a settlement plan in 6-decimal base units, and nothing is executed. Slightly incomplete in not explaining what the settlement plan contains or how long a quote remains valid.

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?

Schema coverage is 100% for the single amountUsd parameter, so the schema already documents the input. The description adds only the downstream interpretation (6-decimal base units) rather than input semantics, so the baseline 3 applies.

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 (quote) plus resource (payment) and spells out exactly what the call does: converts a USD amount to USDG base units at 6 decimals and returns a settlement plan. The closing 'without executing' implicitly distinguishes it from the mutating sibling pons_pay, so an agent can route correctly.

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?

'Without executing' implies this is the pre-flight/preview step, but the description never names pons_pay or states when to prefer quoting over paying, nor any precondition (e.g., run this before every pons_pay). Usage is only implied.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.