Skip to main content
Glama

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

/pack/buy/starter

[x402 paid: $2.990 USDC on Base] Prepaid pack 'starter': 500 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/starter"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/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 substantial work: it discloses the exact price and currency ($2.990 USDC on Base), the x402 payment mechanism, the credit accounting rule (1 credit = 1 call priced up to $0.005, pricier endpoints cost ceil(price/0.005) credits), and how to verify balance. It omits whether purchases are idempotent, whether credits expire, and whether payment is refundable, which matter for a spend operation.

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 paragraph with no filler sentences; price and pack size are front-loaded, followed by the acquisition flow and the credit accounting rule. The parenthetical formula is compact for the concept it conveys, though the run-on structure packs several distinct ideas into one block.

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?

There is no output schema, but the description compensates by explaining that tools/call returns the live payment challenge and by pointing to the balance endpoint for verification. For a payment/commerce tool the key facts (price, network, protocol, credit math, key usage) are present; edge cases like credit expiry or partial refunds remain unspecified.

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, so the baseline is 4. The description still adds useful meaning by documenting the pack_key that the purchase yields and where it is consumed (X-Pack-Key header, /pack/balance?key=), giving the agent context for the value returned even without a schema.

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 transaction ('Buy once via x402') and its concrete deliverable ('Prepaid pack \'starter\': 500 API credits'), with an explicit price. It distinguishes this pack by name and credit allotment, though it never explicitly contrasts with /pack/buy/pro or /pack/buy/business, so the agent must infer the tier difference from the pack label alone.

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?

It gives clear post-purchase instructions: call /api/* and /execute/* with header X-Pack-Key, and check balance at /pack/balance?key=<pack_key>. It also tells the agent that tools/call surfaces the live payment challenge, which explains where the buy step fits in the flow. What is missing is when to prefer this pack over the sibling pro/business packs.

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