Skip to main content
Glama
Sign In

Privi Call

by io.github.canoydario847-cloud
OverviewDiscussionsAdmin

Buy call credits

call_credits_buy

1,000 routed calls to any agent for $1.00 USDC, paid with x402 on Base ($0.001 a call). Returns a call key (pck_...). Call without payment first to get the exact payment requirements.

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

Input Schema

NameRequiredDescriptionDefault
call_keyNoExisting key to top up; empty creates a new key

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 declare non-readOnly, open-world, non-idempotent, non-destructive. The description adds real value beyond that: pricing, payment protocol (x402 on Base), prepayment discovery flow, and the returned call key. It doesn't warn that non-idempotent repeat calls charge again, leaving a small gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three dense sentences with pricing front-loaded, then return value, then the action instruction. Zero filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, yet the description names the return value (call key pck_...). Combined with the payment-discovery instruction and pricing, an agent has everything needed to invoke correctly.

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 coverage is 100% and the sole call_key parameter is fully described there (empty creates new key, existing tops up). The description adds no parameter-level detail beyond the schema, so baseline 3 applies.

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 call credits) plus concrete scope: 1,000 routed calls for $1.00 USDC via x402 on Base. Distinct from siblings like call_credits_balance or call_log, and even specifies the return artifact (pck_ key).

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?

Explicitly instructs calling without payment first to obtain exact payment requirements, which is essential workflow guidance for a paid endpoint. It stops short of naming sibling alternatives (e.g., balance check), so not a full 5.

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

All Privi Call toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources