Skip to main content
Glama

Buy an Iris Credits pack with x402 / MPP over MCP

buy_credit_pack

Buy prepaid credits in one payment: starter $0.250 = 60 credits (3 essay markings), 7 days; class $1.000 = 300 credits (15 essay markings), 30 days; term $5.000 = 1800 credits (90 essay markings), 90 days. PAID with x402 over MCP (USDC on Base) or MPP over MCP (USDC.e on Tempo); the result contains the key. No crypto client? Use the free credits_quote + credits_claim tools to buy the same packs with a plain USDC transfer from any wallet.

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

Input Schema

NameRequiredDescriptionDefault
packNoWhich pack (default starter)
labelNoOptional name for the key, e.g. a class (max 60 characters)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already flag the safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=true, idempotentHint=false), so the description's job is to add context — which it does by naming both payment rails (x402 on Base with USDC, MPP on Tempo with USDC.e) and disclosing that the result contains the key. It stops short of telling the agent that repeated calls charge money again or what happens on payment failure.

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?

Front-loaded with the concrete offer and pricing, then the payment rails, then the fallback — a sensible information order. The middle is a semicolon-chained run-on that could be split, but every clause carries real information.

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 two-parameter, zero-required purchase tool with no output schema, the description covers pricing, rails, the returned key, and the no-crypto fallback. Remaining gaps (failure/refund behavior, whether the key is delivered only on payment success) are minor but not trivial for a tool that spends real money.

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 description coverage is 100%, so the enum values and the label parameter are already documented structurally; baseline 3 applies. The prose does add meaning to the pack values by pairing each with price, credit count, and duration, but the label parameter is never mentioned in the description.

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 and resource ("Buy prepaid credits in one payment") and enumerates the exact three packs with prices, credit counts, essay-marking equivalents, and validity windows. An agent can tell immediately that this is the paid, immediate-purchase path, as opposed to the quote/claim flow named later in the text.

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

Usage Guidelines5/5

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

Gives an explicit decision rule and names the alternative: if the caller has no crypto client, use credits_quote + credits_claim with a plain USDC transfer. The conditions that select each path are stated rather than inferred.

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