Skip to main content
Glama
Sign In

agent-audit + page-read (x402)

by io.github.agent-audit-x402
OverviewDiscussionsAdmin

Is this quote on that page?

quote_check
Read-only

Paid, $0.005 USDC on Base via x402 (agent-audit). Fetches the page now and reports whether the quote is really there: found_exact/found_near/partial/not_found/page_unavailable, similarity, context and page sha256. Call without payment to get the x402 requirements.

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": {
      "url": "<url>",
      "quote": "<quote>"
    },
    "name": "quote_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes
quoteYes
paymentNoOptional. A signed x402 v2 PaymentPayload for this tool's PaymentRequired (as an object, or base64 as in the PAYMENT-SIGNATURE HTTP header). Prefer params._meta["x402/payment"]. Omit it to get the exact payment requirements first.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Annotations only cover the safety profile (readOnly, non-destructive, open-world, non-idempotent); the description adds materially more: the exact price and chain/rail ($0.005 USDC on Base via x402), that the page is fetched at call time, and the full enumeration of return statuses plus similarity/context/sha256. This is behavior an agent cannot derive from the annotations or schema.

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?

Three tight sentences, no filler, and the critical call-without-payment instruction is placed last where it is easy to act on. Slightly off-balance in that pricing leads ahead of the tool's actual purpose.

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 does the necessary work of enumerating return fields, and the payment path is explained. Minor gaps remain: matching semantics for the quote and whether payment is charged per call or only on success.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 33% – only `payment` is documented, and the description merely restates the payment handshake that the schema already explains. The required `url` and `quote` parameters get no added semantics (matching mode, normalization, length limits, or error behavior), so the description does not compensate for the coverage gap.

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+resource: fetches the live page and verifies whether a given quote is present, naming the exact result vocabulary (found_exact/found_near/partial/not_found/page_unavailable). No sibling (read_page, preview_page, check_links) does quote verification, so the tool is trivially distinguishable.

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?

"Call without payment to get the x402 requirements" gives concrete invocation sequencing for the paid handshake, which is the main usage trap here. It does not, however, state when to prefer this over read_page/preview_page or any exclusions.

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

All agent-audit + page-read (x402) 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