Skip to main content
Glama
Sign In

Lumi Trades: x402 seller checks and test-buys

by io.github.cypher-osiris
OverviewDiscussionsAdmin

Lumi: free samples of every paid product

lumi_samples
Read-only

Free. A truncated, clearly labelled SAMPLE of each paid product (high_value_check, vendor report) with its USD price and full URL, so you can see the shape and quality before paying. Lists are cut to 2 entries; up to 10 minutes old. Pass route to get one product.

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

Input Schema

NameRequiredDescriptionDefault
routeNoOptional product route, e.g. high_value_check or vendor_report

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / route / description
      Previous value: -"Optional product route, e.g. trust_check or vendor_report"New value: +"Optional product route, e.g. high_value_check or vendor_report"
  2. Changed1 schema field changed
    • changedInput schema / properties / route / description
      Previous value: -"Optional product route, e.g. institutional or funding"New value: +"Optional product route, e.g. trust_check or vendor_report"
  3. Changed1 schema field changed
    • changedInput schema / properties / route / description
      Previous value: -"Optional product route, e.g. institutional or market"New value: +"Optional product route, e.g. institutional or funding"
  4. Changed1 schema field changed
    • changedInput schema / properties / route / description
      Previous value: -"Optional product route, e.g. institutional or signal"New value: +"Optional product route, e.g. institutional or market"
  5. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, openWorldHint), yet the description still adds meaningful behavior: results are cut to 2 entries, data is at most 10 minutes old, samples are explicitly labelled as truncated, and entries carry price plus full URL. That is real added context beyond the structured fields, short only of rate-limit or error behavior.

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-loaded with 'Free.' and then the concrete payload, with no filler sentences. The telegraphic style ('Free.', 'Lists are cut to 2 entries') is efficient, though it reads slightly fragmented rather than fully polished prose.

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 correctly takes on the job of describing returns: label, price, URL, truncation to 2, and freshness window. An agent knows what it will get and how much of it; only the multi-product vs single-product response shape for the route parameter is left implicit.

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% and the single parameter already documents the optional route with an example and pattern. The description adds a small but useful nuance — passing route returns one product, implying omitting it returns all samples — but that is a modest increment over the schema baseline.

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?

The description states precisely what the tool returns: a truncated, clearly labelled sample of each paid product (high_value_check, vendor report) including USD price and full URL. That is a specific resource with concrete contents, though it never names which sibling to use for the full (paid) data, so differentiation is implied rather than stated.

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?

'So you can see the shape and quality before paying' gives a clear situational context (pre-purchase preview), and 'Pass route to get one product' explains the focused-read pattern. However, no alternative is named (e.g. lumi_catalog for the full list) and there is no explicit when-not guidance, so the agent must infer 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