Skip to main content
Glama
Sign In

x402 Checker (AI Nock)

by io.github.nock-for-mak
OverviewDiscussionsAdmin

bid

Paid $0.05 USDC exact on Base: bid on the pay-to-rank board. Each verified bid ADDS to that origin's 24h total. Listing URL must return HTTP 402 (or be this origin). http(s) only. No telegram/discord/whatsapp. payTo 0x3903F05a17676566958B0a3E0c21E0bd49B66ea0. REST POST /bid is the same SKU.

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>"
    },
    "name": "bid"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYeshttp(s) listing URL that returns HTTP 402, or this origin.
nameNoOptional short name. Max 80 chars.
slotNoOptional slot. Max 40 chars.
topicNoOptional topic. Max 40 chars.
descriptionNoOptional one-line description. Max 200 chars.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior5/5

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

It discloses that this is a paid operation ($0.05 USDC exact on Base), provides the payTo address, and details the side effect of adding to the origin's 24h total. These details go far beyond the annotations, which only signal non-read-only and open-world behavior. There is no contradiction with annotations.

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 description is compact and front-loaded with the core purpose and cost, then moves to constraints and payment details. Every sentence adds value, though the single dense paragraph could benefit from light structuring.

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?

For a paid, blockchain-backed write operation with no output schema, the description should explain how payment is executed and what a successful result looks like. It covers cost, destination, and URL eligibility but omits confirmation/response semantics, leaving an agent uncertain about post-conditions.

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 the baseline is 3. The description does not add meaningful semantics to the optional parameters; for 'url' it only restates the schema's HTTP 402/origin constraint. It does not compensate with new information about the optional fields.

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?

The description states a specific action ('bid on the pay-to-rank board') and gives precise scope: the bid costs $0.05 USDC on Base and each verified bid adds to that origin's 24h total. This makes the tool's purpose unmistakable and clearly distinguishes it from sibling tools.

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?

The description provides clear eligibility criteria for the URL parameter (must return HTTP 402 or be this origin, http(s) only, no telegram/discord/whatsapp) and notes the REST POST /bid equivalence. It does not explicitly name sibling alternatives, but the constraints define when the tool can be used.

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

All x402 Checker (AI Nock) 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