Skip to main content
Glama

get_payment_quote

Get a fee estimate for a payment on a specific network. Returns the protocol fee percentage and estimated total. No authentication required.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_payment_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden; it usefully discloses that no authentication is required and what values come back. It omits other traits an agent needs: whether the quote is time-bound/expiring, whether it is a pure read with no side effects, and any rate limits.

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?

Three short sentences, front-loaded with the purpose, then return values, then the auth note. Little waste; only the mismatch with the empty schema keeps it from being fully clean.

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?

For a zero-parameter, no-output-schema tool the description does cover what is returned, so no output schema is needed. However, it implies a network input that does not exist in the schema, leaving an agent unsure how to request a quote for a particular network.

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?

The input schema has zero properties, which normally sets a baseline of 4, but the description refers to 'a payment on a specific network' as if a network selector were an input, while no such parameter exists. That dangling reference adds ambiguity rather than meaning about any parameter.

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?

Uses a specific verb+resource ('Get a fee estimate for a payment') and names the scope ('on a specific network'), plus what is returned (protocol fee percentage and estimated total). It does not explicitly contrast with siblings like compare_chain_fees or estimate_gas, so it stops short of a 5.

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 only implied: an agent can infer this is a pre-payment fee check, but there is no explicit when-to-use, when-not-to-use, or named alternative (e.g. compare_chain_fees for multi-network comparison). No prerequisites or ordering relative to create_payment are stated.

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