Skip to main content
Glama

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

/pack/buy/business

[x402 paid: $24.990 USDC on Base] Prepaid pack 'business': 6000 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/business"
  }
}

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 burden and does much of it: it discloses the exact price and currency, the payment rail (x402 on Base), the prepaid/one-time nature, the credit-consumption formula (ceil(price/0.005)), and where to check balance. It omits expiry, refundability, and whether the purchase is reversible, 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 identity are front-loaded, followed by the payment mechanism and usage details in a compact block. It is dense with parenthetical detail but every sentence carries operational information; no filler.

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-parameter purchase tool with no output schema, the description covers price, credit amount, payment rail, consumption math, key usage, and balance checking — enough to call it and use the result. Remaining unknowns (expiry, refunds, failure modes beyond the live challenge) are secondary for this tool's complexity.

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 schema is trivially complete. The description adds relevant non-schema detail — the X-Pack-Key header and the balance lookup endpoint — which helps the agent use the result even though it does not map to any parameter.

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 opens with a specific verb+resource: buying the prepaid 'business' pack for 6000 API credits at $24.990 USDC on Base. The tier name and credit count implicitly distinguish it from /pack/buy/pro and /pack/buy/starter, but it never explicitly contrasts sizes/tiers, so an agent must infer the difference from the numbers.

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 conveys the implied workflow — buy once via x402, then call /api/* and /execute/* with the X-Pack-Key header — which is useful context. However, it gives no guidance on when to select 'business' over 'pro' or 'starter', nor any prerequisite or fallback advice, leaving tier choice to inference.

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