ai-agent-hub

Call qr-batch (paid)

call_qr_batch

Real batch QR code generator (PNG data URLs), self-hosted — a third-party service registered on this platform, paid via x402 (flat $0.10 per call, production networks). Call without paymentHeader first to receive the price + payment requirements; retry with paymentHeader set to a signed X-PAYMENT value to get the result.

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_qr_batch"
  }
}

Input Schema

Name	Required	Description	Default
`body`	No	For POST calls: JSON body to send
`method`	No	HTTP method this service expects — check its description or try GET first	GET
`queryParams`	No	For GET calls: query-string parameters as key/value pairs
`paymentHeader`	No	Signed x402 X-PAYMENT payload (base64). Omit on first call.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 7, 2026

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 well: it discloses the pay-per-call model (flat $0.10), the x402 payment protocol, production networks, the two-step payment handshake, and the PNG data-URL return format. It omits failure modes and rate limits, so not a 5.

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 front-loaded sentences that lead with what the tool is before the payment workflow. Minor clutter ('self-hosted — a third-party service registered on this platform') but no wasted sentences.

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?

Covers the paid-invocation flow and the return shape adequately (no output schema exists), but gives no guidance on what QR content must be passed in the free-form body/queryParams, which is a real gap for a nested-object tool the agent must construct.

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 description coverage is 100%, so baseline is 3. The description clarifies the paymentHeader lifecycle (omit first, then supply signed X-PAYMENT), but the schema already says 'Omit on first call,' so the added value over structured fields is marginal, and body/queryParams usage is not elaborated.

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 ('Real batch QR code generator (PNG data URLs)') and even the output format. No sibling tool competes for the QR-generation role, so the agent can identify this immediately from the name and description without opening the schema.

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?

Gives an explicit two-step calling flow: call without paymentHeader first to get price/requirements, then retry with a signed X-PAYMENT value. This is strong operational guidance, though it does not state when to prefer this paid batch tool over alternatives or any prerequisites beyond payment.

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

All ai-agent-hub tools Inspect

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

Need Help?