Skip to main content
Glama

Thread Kit: posts that fit every network

How to pay (free)

payment_options
Read-onlyIdempotent

FREE. Receiving address, prices and how to pay the paid tools: x402 over MCP (USDC on Base, per call), or the same endpoints over plain HTTP x402 / MPP.

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": "payment_options"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds two things beyond that: the call itself is free, and it covers two payment rails (MCP x402 and HTTP x402/MPP). It does not say whether the returned prices are static or time-sensitive.

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?

A single compact statement with the most decision-relevant fact ("FREE") front-loaded. The protocol enumeration is dense but each clause carries distinct information; no filler sentences.

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 zero-parameter, read-only info tool with no output schema, the description covers what it returns (address, prices, payment methods) and under which rails. Only the volatility of pricing data is left unaddressed.

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?

The tool takes zero parameters, so the baseline is 4. The schema is empty with additionalProperties=false, consistent with the parameterless description.

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?

The description states a specific resource and content: a receiving address, prices, and how to pay for the paid tools, plus the two transport/protocol paths (x402 over MCP with USDC on Base, or plain HTTP x402 / MPP). It is clearly a payment-info tool, distinct from the writing/length siblings, though the protocol jargon makes the purpose slightly harder to parse at a glance.

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?

"FREE" plus "how to pay the paid tools" implies when to call it: before or when a paid tool requires payment. There is no explicit when-not or named alternative, and no statement of whether prices change or how often to re-check.

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