Skip to main content
Glama
Sign In

Lumi Trades: x402 seller checks and test-buys

by io.github.cypher-osiris
OverviewDiscussionsAdmin

Lumi: price check without paying (free)

lumi_quote
Read-only

Free. Shows the x402 price quote (XRP / RLUSD / USDC on the XRP Ledger, USDC on Base, USDC on Stellar) for any Lumi paid path, e.g. /v1/trust/check/high-value?url=...&amount=10, without paying. A 503 means the data is not fresh right now and the call would not be sold.

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": {
      "path": "<path>"
    },
    "name": "lumi_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesPaid API path, e.g. /v1/trust/check/high-value?url=...&amount=10 or /v1/trust/vendors/printmoneylab/report

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / path / description
      Previous value: -"Paid API path, e.g. /v1/trust/check?url=... or /v1/verdict?url=..."New value: +"Paid API path, e.g. /v1/trust/check/high-value?url=...&amount=10 or /v1/trust/vendors/printmoneylab/report"
  2. Changed1 schema field changed
    • changedInput schema / properties / path / description
      Previous value: -"Paid API path, e.g. /v1/trust/check?url=... or /v1/funding"New value: +"Paid API path, e.g. /v1/trust/check?url=... or /v1/verdict?url=..."
  3. Changed1 schema field changed
    • changedInput schema / properties / path / description
      Previous value: -"Paid API path, e.g. /v1/market or /v1/trust/check?url=..."New value: +"Paid API path, e.g. /v1/trust/check?url=... or /v1/funding"
  4. Changed1 schema field changed
    • changedInput schema / properties / path / description
      Previous value: -"Paid API path, e.g. /v1/brief or /v1/signal/XRP"New value: +"Paid API path, e.g. /v1/market or /v1/trust/check?url=..."
  5. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Beyond the readOnly/openWorld annotations the description adds meaningful behaviour: the call is free, returns a quote rather than the paid payload, and a 503 signals stale data with no sale. It does not cover caching, rate limits, or what a successful quote body looks like, so it is strong but not exhaustive.

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 short sentences, front-loaded with "Free." as the key differentiator, then the mechanism, then the failure mode. No sentence is filler.

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?

With no output schema, the description carries return-value explanation and does so by naming the quote as an x402 price across five chain/asset pairs and explaining the 503 outcome. A brief note on quote expiry or response shape would close the remaining gap, but an agent can call this correctly as written.

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 the single `path` parameter already carries a pattern and sample value, so the baseline is 3. The description's inline example path and the supported chain/asset list add some colour but not new meaning about the parameter's format or constraints.

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 uses a specific verb ("Shows the x402 price quote") and names the exact resource (any Lumi paid path) plus the supported settlement assets. It implicitly distinguishes itself from its paid siblings by stating "without paying", so an agent knows this is the quote-only variant.

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?

It gives a clear context for use: price checking before committing to a paid Lumi path, and flags the 503 case meaning data is stale and the call would not be sold. It never names a concrete alternative among the ten siblings (e.g. lumi_catalog or the paid endpoints), so the when-not guidance is implied rather than explicit.

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