Skip to main content
Glama
Sign In

Lumi Trades: x402 seller checks and test-buys

by io.github.cypher-osiris
OverviewDiscussionsAdmin

Lumi: high value check (paid)

lumi_high_value_check
Read-only

Paid: 0.5% of the stated amount, min $0.005, max $0.25 (e.g. $0.05 for amount=10), per call over x402. Before a larger x402 payment: the same label, allow / warn / block verdict and score as the free lumi_trust_check (paying never changes them), plus a live re-check of the seller at call time and a Lumi-signed receipt bound to the stated amount. Pass url and the USD amount you are about to pay (and optionally the payTo in its quote). The exact price for your amount is in the x402 quote (see lumi_quote).

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

Input Schema

NameRequiredDescriptionDefault
urlYesThe x402 resource URL you are about to pay
payToNoOptional: the payTo address in its 402 quote
amountYesThe USD amount you are about to pay, e.g. 10 (sets the price of this check)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only cover readOnly/openWorld; the description adds the things an agent actually needs: this call costs money over x402 (0.5%, min $0.005, max $0.25, with a worked example), that paying does not change the verdict, that the seller is re-checked live at call time, and that a signed receipt bound to the stated amount is produced. That is substantive cost/auth and output-consequence disclosure absent from structured fields.

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?

Single dense paragraph that front-loads cost and then purpose, with zero filler. The second half is one long compound sentence, which is slightly heavy but every clause carries information.

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?

No output schema exists, and the description compensates by naming the return contents (label, verdict, score, live re-check, signed receipt). Combined with pricing, prerequisites (payTo from the 402 quote) and the sibling pointer, 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 description coverage is 100% and each parameter is already documented in the schema, so the baseline is 3. The description reinforces the intent (pass url plus the USD amount you are about to pay, optionally the payTo) and ties amount to price, but adds little semantic detail the schema does not already carry.

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 action (a paid pre-payment check on an x402 resource) and explicitly contrasts it with the free sibling: 'the same label, allow / warn / block verdict and score as the free lumi_trust_check (paying never changes them), plus a live re-check ... and a Lumi-signed receipt.' An agent can tell exactly what extra it buys over lumi_trust_check 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 Guidelines4/5

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

'Before a larger x402 payment' gives a clear trigger condition, and naming the free equivalent plus a pointer to lumi_quote for exact pricing helps routing. It stops short of an explicit exclusion rule (e.g. 'for small amounts use lumi_trust_check instead'), leaving the threshold to inference.

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