Skip to main content
Glama
Sign In

Lumi Trades: x402 seller checks and test-buys

by io.github.cypher-osiris
OverviewDiscussionsAdmin

Lumi: seller monitoring plans and monitored sellers (free)

lumi_seller_monitoring
Read-only

Free. Seller monitoring for x402 sellers: Watch and Watch Pro plans per endpoint per 30 days, a one-off audit, test-buy packs, a free Watch tier and a 14-day Watch trial (prices are returned by this tool and in each 402). No auto-renew; payTo proven by signature; paying never changes a score. No args: plans, enrolment steps and safeguards. enrollment_id: that seller's public entry (disclosure, findings, replies) and live badge status. Plans are paid over x402 at the REST URL.

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_seller_monitoring"
  }
}

Input Schema

NameRequiredDescriptionDefault
enrollment_idNoOptional enrollment id (men_...)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Beyond the readOnly/openWorld annotations, the description discloses pricing behavior, no auto-renew, signature-proven payTo, and that payment never changes a score. It also clarifies that payment occurs over x402 at the REST URL rather than through the tool itself.

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?

The description is dense but front-loaded and most clauses carry useful information about modes, pricing, and payment safeguards. It is somewhat telegraphic and semicolon-heavy, which slightly reduces readability despite being concise.

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?

For a read-only, one-optional-parameter tool with no output schema, it provides enough context about what is returned, how billing works, and what safeguards apply. It does not fully describe the response shape, but it covers the key invocation and behavioral details.

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% and the single parameter is already documented there, but the description adds meaningful semantics: an enrollment_id selects that seller's public entry with disclosure, findings, replies, and live badge status. This goes beyond the schema's bare 'Optional enrollment id' description.

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 the resource specifically: seller monitoring plans and monitored seller entries for x402 sellers, including the two invocation modes. It is clear what the tool returns, but it does not explicitly distinguish itself from sibling trust/check/report tools.

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 clearly explains the argument-dependent behavior: no args returns plans, enrolment steps and safeguards, while enrollment_id returns that seller's public entry and badge status. It gives usable context, though it does not explicitly route agents away from sibling tools.

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