Skip to main content
Glama

LION - keyless x402 data + RPC for agents

by dev.workers.lionmaster-operations.lion-x402
OverviewDiscussionsAdmin

lion_composite_bundle

Multi-chain keyless RPC + Ed25519-attested enrichment, one call [x402 paid: GET /api/x402/composite-bundle-json price $0.001 on Base]

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
chainNo
identifierNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Changed7 schema fields changed
    • removedInput schema / properties / address
      Removed value: -{
-  "description": "0x... address -> eth_getBalance + eth_getCode (native balance + contract flag), per chain.",
-  "type": "string"
-}
    • removedInput schema / properties / chain / description
      Removed value: -"Which chain(s) to read: base (default), ethereum (eip155:1), or both. Payment is always USDC on Base."
    • removedInput schema / properties / chain / enum
      Removed value: -[
-  "base",
-  "ethereum",
-  "both"
-]
    • removedInput schema / properties / fields
      Removed value: -{
-  "description": "Enrich field names to return, e.g. [\"country\",\"revenue_usd\"]. Omit when using format=apollo_org.",
-  "items": {
-    "type": "string"
-  },
-  "type": "array"
-}
    • removedInput schema / properties / format
      Removed value: -{
-  "description": "Apollo-organization-shaped enrich half (pass identifier/domain).",
-  "enum": [
-    "apollo_org"
-  ],
-  "type": "string"
-}
    • removedInput schema / properties / identifier / description
      Removed value: -"Company/org NAME, DOMAIN (e.g. \"coinbase.com\"), or US TICKER for verifiable firmographics + financials."
    • removedInput schema / properties / tx
      Removed value: -{
-  "description": "0x... tx hash -> eth_getTransactionReceipt (status, block, from, to), per chain.",
-  "type": "string"
-}
  4. Changed1 schema field changed
    • addedInput schema / required
      Added value: +[]
  5. Added

TDQS

C2.7/5.0
Behavior3/5

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

With no annotations, the description carries the full disclosure burden, and it does supply genuinely useful behavior: keyless access (no API key), and x402 paid at $0.001 on Base. Missing are auth mechanics beyond 'keyless', rate limits, and what happens when optional params are omitted.

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?

A single tight sentence with the capability statement front-loaded and the payment detail bracketed as secondary. Nothing is padded, though the compressed jargon trades clarity for brevity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema, no annotations, and both parameters undocumented leaves too much unresolved for a paid multi-purpose bundle. The description does not say what the enrichment covers, what the return shape is, or how partial results are handled.

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

Parameters2/5

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

Schema coverage is 0% for two parameters, and the description never mentions 'chain' or 'identifier'. The agent cannot tell whether identifier is a wallet, tx hash, domain, or entity name, nor what values 'chain' accepts, so the description fails to compensate for the schema gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the two bundled capabilities ('keyless RPC' and 'Ed25519-attested enrichment') and scopes them as multi-chain, which partly separates it from lion_keyless_base_rpc. However, there is no clear action verb or statement of what the composite result actually is, and 'composite bundle' remains jargon an agent must interpret.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

No when-to-use guidance, no conditions under which this bundle should be chosen over lion_keyless_base_rpc or lion_enrichment_tx_bundle, and no exclusions. The only routing signal is the price bracket, which tells the agent this call costs money but not when it is worth making.

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

All LION - keyless x402 data + RPC for agents 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