Skip to main content
Glama
Sign In
Lumière PayCheck

Lumière PayCheck

by Book0fEli
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Most trustworthy x402 endpoints

top_endpoints
Read-onlyIdempotent

Lists x402 endpoints currently safe to pay, ordered by safety score and showing grade, verdict, and whether a real test payment succeeded. Use it to discover reliable endpoints or compare providers.

Instructions

List the x402 endpoints that are currently safest to pay (verdict proceed or caution, no payout-wallet incidents), best first, with score, grade, verdict, and whether a real test payment was delivered. Use it to discover reliable endpoints or pick between providers. To evaluate one specific endpoint use check_endpoint; to approve a payment use check_payment. Read-only and free; rankings update as monitoring runs (every 30 minutes).

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

Input Schema

NameRequiredDescriptionDefault
limitNoHow many endpoints to return, 1-50 (default 10)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so 'read-only' is partly redundant. The description still adds real context beyond them: the tool is free, rankings refresh on a 30-minute monitoring cadence, and 'safest' is operationally defined as proceed/caution verdicts with no payout-wallet incidents.

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 tight sentences, front-loaded with purpose and eligibility, followed by routing and operating constraints. No filler; every sentence contributes.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 enumerates the returned fields (score, grade, verdict, test-payment status) and defines the ranking predicate. Combined with the alternatives routing and freshness note, an agent has everything needed to call it correctly.

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 coverage is 100% with a single optional 'limit' parameter whose bounds and default are fully documented in the schema. The description adds no syntax or format detail beyond that, so the baseline of 3 is appropriate.

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 ('List') and resource ('x402 endpoints that are currently safest to pay'), defines the inclusion criteria (verdict proceed or caution, no payout-wallet incidents), the ordering ('best first'), and the returned fields. An agent can distinguish it from check_endpoint or check_payment without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly names the use cases ('discover reliable endpoints or pick between providers') and routes to alternatives with conditions: check_endpoint for one specific endpoint, check_payment to approve a payment. Both the when-to-use and when-not-to-use are covered.

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

Deploy Server

Other Tools