Skip to main content
Glama

Base Agent Due-Diligence Kit

How to pay (free)

payment_options
Read-onlyIdempotent

FREE. Receiving address, prices and the two ways to pay for the paid tools: x402 (USDC on Base, per call) or one plain USDC transfer of 0.25 that unlocks every paid tool for 24h (no x402 client needed).

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.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the bar is lower; the description nonetheless adds real behavioral context by disclosing that the call is free, that prices are included in the response, the chain and asset for payment (USDC on Base), and the 24-hour unlock semantics of the flat 0.25 transfer. It stops short of noting price freshness or whether the address is chain-specific.

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 dense sentence with the key qualifier ('FREE') front-loaded and no filler. Minor friction: '0.25' appears without a unit and the clause stacking around the two payment methods is slightly cramped, but nothing is redundant.

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, annotation-covered tool with no output schema, the description supplies what an agent needs: that the call is free, what it returns, and how each payment option works. Only the response shape (e.g., address format, whether prices are per-tool) is left unstated.

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, which is the baseline-4 case; there is nothing for the description to disambiguate. It correctly spends no words on parameters and instead describes the payload.

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 clearly states what the tool returns: a receiving address, prices, and the two supported payment paths (x402 per-call vs. a one-time 0.25 USDC unlock). It is a noun-phrase enumeration rather than an explicit verb+resource statement, and it does not name any sibling, but an agent can tell this is the payment-information tool rather than a paid analysis tool.

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 leading 'FREE.' signals it is safe to call at no cost, and 'no x402 client needed' hints at which payment path suits an agent without x402 support. However, there is no explicit statement of when to call it (e.g., before invoking a paid tool, or when a payment challenge is received) and no routing away from the x402_preflight sibling, so 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.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources