Skip to main content
Glama

Prices and how to pay (free)

payment_options
Read-onlyIdempotent

FREE. Credit costs and per-call prices of every tool, the credit packs, how to buy a key with a plain USDC transfer on Base (no crypto client needed), how to use the key in an MCP client, the x402 / MPP over MCP retry format, and the balance of the key you are using (if any).

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
keyNoOptional Iris Credits key (iris_ + 48 hex). Better: set it once as the MCP header Authorization: Bearer <key>. Without a key the call is paid with x402 / MPP over MCP.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds meaningful behavior the annotations do not: the call is free, no crypto client is needed to buy a key, the x402/MPP-over-MCP retry format is explained, and it reports the balance of the key in use. It stops short of describing response shape or whether the x402 challenge is returned inline versus as an error.

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 sentence, but the most decision-relevant token ("FREE.") is front-loaded and each clause maps to a distinct piece of information the caller needs. The enumerated list is dense yet free of filler, though the run-on structure slightly reduces scannability.

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 read-only, zero-required-parameter info tool with no output schema, the description enumerates the content an agent will receive well enough to decide whether to call it. The only gap is that it does not say whether pricing data is static or fetched live, and it does not clarify how the x402 challenge is surfaced.

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?

There is one optional parameter with 100% schema description coverage, so the schema already explains the iris_ key format and the Authorization: Bearer alternative. The description only gestures at the key via "the balance of the key you are using (if any)" and adds no format or precedence detail beyond the schema. Baseline 3 applies when the schema does the heavy lifting.

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 names a specific resource — credit costs, per-call prices, credit packs, key purchase via USDC on Base, MCP key usage, x402/MPP retry format, and current key balance. That is concrete enough for an agent to know this is a pricing/documentation tool rather than an action tool. It does not name the sibling tools (credits_quote, credits_status, buy_credit_pack) whose scope partly overlaps, so differentiation is left to inference.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

Leading with "FREE." gives a clear contextual signal that this is the no-cost way to learn prices and payment mechanics before spending credits. However, it never explicitly states when to prefer this over credits_quote or credits_status, nor any exclusions.

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