Skip to main content
Glama

LION - keyless x402 data + RPC for agents

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

lion_adaptive_query

Multi-source on-chain + market intelligence (dex, risk, yields, wallet, holders, rpc) [x402 paid: GET /api/x402/adaptive-query price $0.005 on Base]

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNo
modeNoauto|rpc|domain|social
domainNo
methodNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Changed10 schema fields changed
    • removedInput schema / properties / address
      Removed value: -{
-  "description": "Base address (0x...) for source=base_rpc_read or source=wallet_profile.",
-  "type": "string"
-}
    • removedInput schema / properties / chain
      Removed value: -{
-  "description": "Which chain: base (default) or ethereum. Data is multi-chain; payment stays USDC on Base.",
-  "enum": [
-    "base",
-    "ethereum"
-  ],
-  "type": "string"
-}
    • addedInput schema / properties / domain
      Added value: +{
+  "type": "string"
+}
    • addedInput schema / properties / method
      Added value: +{
+  "type": "string"
+}
    • addedInput schema / properties / mode
      Added value: +{
+  "description": "auto|rpc|domain|social",
+  "type": "string"
+}
    • addedInput schema / properties / q
      Added value: +{
+  "type": "string"
+}
    • removedInput schema / properties / source
      Removed value: -{
-  "description": "Which live onchain source to query.",
-  "enum": [
-    "base_dex",
-    "token_risk",
-    "defi_yields",
-    "base_rpc_read",
-    "wallet_profile",
-    "token_holders"
-  ],
-  "type": "string"
-}
    • removedInput schema / properties / token
      Removed value: -{
-  "description": "Base token address (0x...) for source=token_risk or source=token_holders.",
-  "type": "string"
-}
    • removedInput schema / properties / tx
      Removed value: -{
-  "description": "Base transaction hash (0x...) for source=base_rpc_read.",
-  "type": "string"
-}
    • addedInput schema / required
      Added value: +[]
  4. Changed2 schema fields changed
    • addedInput schema / properties / chain
      Added value: +{
+  "description": "Which chain: base (default) or ethereum. Data is multi-chain; payment stays USDC on Base.",
+  "enum": [
+    "base",
+    "ethereum"
+  ],
+  "type": "string"
+}
    • changedInput schema / properties / source / description
      Previous value: -"Which live Base onchain source to query."New value: +"Which live onchain source to query."
  5. Changed5 schema fields changed
    • addedInput schema / properties / address
      Added value: +{
+  "description": "Base address (0x...) for source=base_rpc_read or source=wallet_profile.",
+  "type": "string"
+}
    • changedInput schema / properties / source / description
      Previous value: -"Which LION data source to query: base_dex, token_risk, defi_yields, wallet_intent, ai_tools."New value: +"Which live Base onchain source to query."
    • addedInput schema / properties / source / enum
      Added value: +[
+  "base_dex",
+  "token_risk",
+  "defi_yields",
+  "base_rpc_read",
+  "wallet_profile",
+  "token_holders"
+]
    • changedInput schema / properties / token / description
      Previous value: -"Base token address (0x...) when source=token_risk."New value: +"Base token address (0x...) for source=token_risk or source=token_holders."
    • addedInput schema / properties / tx
      Added value: +{
+  "description": "Base transaction hash (0x...) for source=base_rpc_read.",
+  "type": "string"
+}
  6. First observed

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 burden, and it does disclose one important behavioral trait: this is an x402 paid endpoint (GET /api/x402/adaptive-query, $0.005 on Base), which an agent needs to know before calling. It stops short of describing return shape, latency, or rate limits.

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 front-loaded sentence that leads with capability and appends the payment metadata in a bracket. Efficient, though the parenthetical domain list and the bracket are densely packed together.

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?

For a four-parameter tool with no output schema and no annotations, the description is inadequate: it never explains what the tool returns, how 'q' relates to 'domain'/'method', or what the mode values do. An agent has too little to invoke it confidently.

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 description coverage is only 25% (only 'mode' is documented), so the description must compensate. It loosely maps the listed domains to the 'domain' parameter but says nothing about 'q' (the core query input) or 'method', leaving three of four parameters semantically unexplained.

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 identifies the resource as 'multi-source on-chain + market intelligence' and enumerates the domains it spans (dex, risk, yields, wallet, holders, rpc). However, it offers no specific verb describing the operation, and 'adaptive query' is broad enough that the agent cannot tell how this differs from siblings like lion_quick_intel or lion_token_risk_indicators.

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?

There is no guidance on when to use this tool versus the many lion_* siblings, no prerequisites, and no exclusions. The mode parameter ('auto|rpc|domain|social') hints that behavior varies, but the description never explains which mode applies when.

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