Skip to main content
Glama

MNOGO DENEG — pay-per-call crypto & AI APIs (x402)

/pack/buy/pro

[x402 paid: $9.990 USDC on Base] Prepaid pack 'pro': 2000 API credits. Buy once via x402 (USDC on Base), then call /api/* and /execute/* with header X-Pack-Key. 1 credit = 1 call priced up to $0.005 (pricier endpoints cost ceil(price/0.005) credits). Balance: /pack/balance?key=<pack_key> tools/call returns the live payment challenge.

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": "/pack/buy/pro"
  }
}

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?

With no annotations, the description carries the full load and does well: it discloses the $9.990 USDC-on-Base x402 payment requirement, the credit economics (1 credit = 1 call up to $0.005, with ceil(price/0.005) for pricier endpoints), and that tools/call surfaces the live payment challenge. It stops short of stating whether purchases are idempotent, refundable, or whether the pack key expires, which are meaningful gaps for a paid mutation.

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?

The price and pack size are front-loaded in the first clause, and each following sentence adds a distinct fact (usage, credit math, balance check). It is dense but nearly every clause earns its place; the x402/protocol jargon slightly raises parsing cost.

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-param paid purchase with no output schema, the definition covers cost, credits, payment rail, consumption model, and how to verify balance. The main missing pieces are what the call returns on success (presumably the pack key) and failure/expiry behavior, but the core calling decision is well supported.

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?

There are zero input parameters, so the baseline is 4. The description still adds operational meaning beyond the schema by documenting the X-Pack-Key header and the ?key=<pack_key> balance query pattern an agent needs after purchase.

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?

States a specific verb and resource: buy the prepaid 'pro' pack granting 2000 API credits, plus the price and rail. It names the tier ('pro') but does not contrast it with the sibling starter/business packs, so differentiation is only implicit through the credit count and price.

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?

It explains the post-purchase workflow ('Buy once via x402, then call /api/* and /execute/* with header X-Pack-Key') and points to /pack/balance for checking remaining credit, which is useful operating context. However, it gives no guidance on when to pick 'pro' over the sibling starter or business packs, leaving tier selection to the agent.

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