Skip to main content
Glama
Sign In

Lumi Trades: x402 seller checks and test-buys

by io.github.cypher-osiris
OverviewDiscussionsAdmin

Lumi: should I pay this x402 URL? (free, rate-limited)

lumi_trust_check
Read-only

Free (rate-limited per client and per day). Should I pay this x402 URL? Start here before any paid tool. One label (checks_passed / check_first / checks_failed / no_data) plus the allow / warn / block verdict with coded reasons, from Lumi's daily CDP Bazaar index, free 402-quote checks and Lumi's own test-buys (Base USDC for Bazaar listings; XRPL only for a small curated vendor list, counted separately). Pass url, and optionally the payTo and USD amount you were quoted, to catch address or price mismatches. Links the free lookup and, for curated vendors, the paid full report. Observations, not a guarantee. Near the top of the result, paid_option names the paid high-value check (lumi_high_value_check; its price is in its own description), which returns the same verdict and score.

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

Input Schema

NameRequiredDescriptionDefault
urlYesThe x402 resource URL you are about to pay
payToNoOptional: the payTo address in its 402 quote
amountNoOptional: the quoted price in USD, e.g. 0.01

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / amount / maxLength
      Added value: +20
    • addedInput schema / properties / payTo / maxLength
      Added value: +120
    • addedInput schema / properties / url / maxLength
      Added value: +500
  2. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, and the description adds meaningful context: free but rate-limited per client and per day, data provenance (daily CDP Bazaar index, free 402-quote checks, own test-buys with Base USDC vs XRPL caveat), and a candid "Observations, not a guarantee" limitation. That is real behavioral value beyond the 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?

Front-loads free/rate-limited status and the core question, then layers provenance and escalation. It is dense and slightly packed with parenthetical detail, but nearly every clause carries decision-relevant information.

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?

No output schema exists, and the description compensates by describing the returned label set, verdict levels, coded reasons, and where paid_option appears in the result. Combined with the caveat and provenance, an agent has enough to call it and interpret the response; only minor gaps remain.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds the reason to supply the optional payTo and amount: to catch address or price mismatches against the quote. That motivates the optional parameters rather than merely restating the schema.

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 concrete verb (check) and resource (an x402 URL before paying it), plus the exact output vocabulary (one label from checks_passed/check_first/checks_failed/no_data with allow/warn/block verdict). It also distinguishes itself from the paid sibling lumi_high_value_check, which returns the same verdict and score.

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?

"Start here before any paid tool" gives explicit ordering guidance, and the description names lumi_high_value_check as the paid escalation path. It doesn't cover when to prefer other siblings like lumi_verdict or lumi_vendor_report, so it stops short of full alternative routing.

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

All Lumi Trades: x402 seller checks and test-buys 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