Skip to main content
Glama

buy

Purchase a new membership of at least 250 questions using USDC on Solana via x402 from the PARANOID_PAYER wallet; pricing is 0.002 USDC per question plus a 0.30 USDC setup fee.

Instructions

Buy a new membership with an x402 payment in USDC on Solana from the wallet in PARANOID_PAYER: 0.002 USDC a question plus a 0.30 USDC setup fee, 250 questions at least. A membership already here that still has questions is kept in a file beside the new one.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "questions": "<questions>"
    },
    "name": "buy"
  }
}

Input Schema

NameRequiredDescriptionDefault
questionsYesHow many questions to buy.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does real work: it discloses that this is a real-money purchase, the exact unit price and setup fee, the chain and currency, and — importantly — that an existing membership with remaining questions is preserved rather than overwritten. It stops short of stating irreversibility, failure/refund behavior, or expected latency for an on-chain payment.

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?

Two dense sentences, front-loaded with the action and cost — the most decision-relevant facts come first. The closing clause 'kept in a file beside the new one' is vaguely worded and costs a re-read, which keeps it from a 5.

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 an unannotated, irreversible spend operation with no output schema, the pricing and state-preservation details are valuable, but gaps remain: what a successful call returns (no output schema to fall back on), what happens if payment fails mid-transaction, and how the payer wallet is supplied. An agent could call this correctly but not predict the result.

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?

Only one parameter and schema coverage is 100%, so the schema already explains 'questions' fully. The description corroborates the minimum ('250 questions at least') and adds per-question pricing that lets an agent compute total cost, but adds no further semantics beyond that baseline.

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 uses a specific verb and resource — 'Buy a new membership' — and qualifies it with the payment rail (x402 in USDC on Solana). It is clearly distinguishable from ask/balance/models by implication, though it never names a sibling or states the boundary explicitly.

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 infers 'call this when you need questions' from the '250 questions at least' clause. There is no guidance on checking balance first, no prerequisites (e.g., needing SOL for fees or how PARANOID_PAYER is configured), and no statement of when not to buy.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools