Skip to main content
Glama

x402 endpoint check

endpoint_check
Read-onlyIdempotent

Check whether an x402 endpoint is safe to pay: it looks at what the endpoint asks you to pay and to whom and compares that with its history. It never pays the endpoint. Unreachable endpoints and bad input are not charged. Free: 1 a day per IP (counted across the HTTP routes and MCP), then $0.005 per call via x402.

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

Input Schema

NameRequiredDescriptionDefault
urlYeshttps URL of the x402 endpoint

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior5/5

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

Goes well beyond the readOnly/idempotent/non-destructive annotations: it states the tool never transfers payment, that failed or malformed calls incur no charge, and it discloses the exact pricing model (1 free/day per IP shared across HTTP and MCP, then $0.005 per call). Those cost and rate-limit facts are exactly the behavioral context an agent needs before invoking a paid tool.

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 sentences, front-loaded with purpose, then the no-payment/no-charge guarantees, then pricing. Efficient overall; the final pricing sentence is dense but every clause (free quota, cross-route counting, per-call price) is actionable information.

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 invocation conditions and cost thoroughly, and annotations carry the safety profile. With no output schema, though, the description never indicates what a verdict looks like (boolean safe/unsafe, risk reasons, payment details), leaving the agent unsure how to interpret the result.

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?

Only one parameter with 100% schema description coverage ("https URL of the x402 endpoint"), so the schema already carries the semantics. The description adds nothing about URL form, host requirements, or validation beyond what the schema states, making baseline 3 appropriate.

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 and resource ("Check whether an x402 endpoint is safe to pay") plus the mechanism: compares the endpoint's payment request and payee against its history. It implicitly distinguishes itself from verify_payment via "It never pays the endpoint," but never names the siblings scam_check or verify_payment directly.

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?

Usage is implied (call this before paying an endpoint), and it usefully notes that unreachable endpoints and bad input are not charged. However, it gives no explicit when-to-use/when-not guidance and does not route the agent between itself, scam_check, and verify_payment.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources