Skip to main content
Glama
Sign In

ZERO Payment Guard

by host.beacon.worker.zero-payment-guard
OverviewDiscussionsAdmin

Batch page extract (up to 10 URLs) ($0.008 USDC on Base via x402)

page_extract_batch
Read-onlyIdempotent

Paid $0.008 per call (x402, USDC on Base). Extract up to 10 public web pages in parallel to clean Markdown + metadata. Per-URL errors are inline; fails (not charged) only if no URL succeeds.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "urls": "<urls>"
    },
    "name": "page_extract_batch"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlsYesPublic http(s) URLs
maxCharsNoMax Markdown chars per page, default 8000

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Goes well beyond the annotations by disclosing the payment requirement (x402, $0.008 USDC on Base), the parallel execution model, per-URL inline error semantics, and the precise billing rule — charged only if at least one URL succeeds. Those failure and cost semantics are exactly the behavior an agent needs when deciding whether to batch.

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 compact sentences, cost front-loaded, then capability, then failure/billing semantics. Zero filler and no repetition of annotation data.

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?

With no output schema, the description carries the return-format burden and does so at a high level ('clean Markdown + metadata' plus per-URL inline errors). What 'metadata' contains and the maxChars interaction across pages are left implicit, a small gap for a paid tool.

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 both 'urls' and 'maxChars' are already documented with types, bounds, and defaults. The description only echoes the URL cap and public-page constraint, adding essentially nothing beyond the schema, which is the baseline-3 case.

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 ('Extract'), resource ('public web pages'), scale ('up to 10 ... in parallel'), and return form ('clean Markdown + metadata'). What's missing is explicit sibling differentiation: the single-page 'page_extract' is never named, so the agent must infer that the batch variant is the multi-URL one from the 'up to 10' phrasing.

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?

No explicit when-to-use or when-not-to-use statement and no named alternative, but the per-call price and the 10-URL cap imply the economics of batching versus repeated single-page calls. Guidance is inferable rather than stated.

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

All ZERO Payment Guard 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