Skip to main content
Glama

UniswapX Order-Flow Evals

sv_uniswapx
Read-only

Orkid solver telemetry over public UniswapX orders: observed orders, achievable vs decayed-required output, executable surplus, funnel decisions across Ethereum/Base/Arbitrum/BSC, plus armed-fill landability sims and the daily realizability funnel (claimed surplus-positive rate vs sim-proven landability). Panels: uniswapx_evals_{chain}, uniswapx_shadow_{chain}, uniswapx_realizability. Params: panel, start/end, limit. Free with X-ORKID-API-Key or $0.02 USDC/call via x402.

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

Input Schema

NameRequiredDescriptionDefault
endNoEnd date YYYY-MM-DD
limitNoMax rows, default 100, cap 500
panelNoPanel to query (default first). Available: uniswapx_evals_ethereum, uniswapx_evals_base, uniswapx_evals_arbitrum, uniswapx_evals_bsc, uniswapx_shadow_ethereum, uniswapx_shadow_base, uniswapx_shadow_arbitrum, uniswapx_shadow_bsc, uniswapx_realizability
startNoStart date YYYY-MM-DD

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / panel / description
      Previous value: -"Panel to query (default first). Available: uniswapx_evals_ethereum, uniswapx_evals_base, uniswapx_evals_arbitrum, uniswapx_evals_bsc, uniswapx_shadow_ethereum, uniswapx_shadow_base, uniswapx_shadow_arbitrum, uniswapx_shadow_bsc"New value: +"Panel to query (default first). Available: uniswapx_evals_ethereum, uniswapx_evals_base, uniswapx_evals_arbitrum, uniswapx_evals_bsc, uniswapx_shadow_ethereum, uniswapx_shadow_base, uniswapx_shadow_arbitrum, uniswapx_shadow_bsc, uniswapx_realizability"
  2. Changed1 schema field changed
    • changedInput schema / properties / panel / description
      Previous value: -"Panel to query (default first). Available: uniswapx_evals_ethereum, uniswapx_evals_base, uniswapx_evals_arbitrum, uniswapx_evals_bsc"New value: +"Panel to query (default first). Available: uniswapx_evals_ethereum, uniswapx_evals_base, uniswapx_evals_arbitrum, uniswapx_evals_bsc, uniswapx_shadow_ethereum, uniswapx_shadow_base, uniswapx_shadow_arbitrum, uniswapx_shadow_bsc"
  3. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds genuinely new behavioral context: it is paid data ($0.02 USDC/call via x402) unless an X-ORKID-API-Key is supplied, and it spans four chains plus simulated landability data. It does not discuss rate limits, caching, or how the sim panels are computed.

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 compact blocks — what the data contains, which panels exist, and which params/access apply — with the most decision-relevant content (panel list) placed before the billing note. Every sentence carries information; there is no boilerplate. The dense jargon is a readability cost but not wasted text.

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

Completeness3/5

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

There is no output schema, so the description must carry the return-shape burden, and it only gestures at columns ('executable surplus', 'funnel decisions') without stating what a row actually contains per panel. For a nine-panel tool with a chain dimension that is a real gap. Auth, cost, panel names, chains and defaults are all covered, so the missing piece is narrowly the per-panel row shape.

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%, so the baseline is 3 and the description's 'Params: panel, start/end, limit' largely repeats the schema. It does add the {chain} naming pattern that groups panels by family, which mildly helps an agent construct a panel value. The limit cap of 500 is stated in both places, and no date-range or panel-specific semantics are added beyond that.

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 names a concrete resource and measurement set: observed UniswapX orders, achievable vs decayed-required output, executable surplus, funnel decisions, armed-fill landability sims, and the realizability funnel. That is specific enough for an agent to know this is a read-only order-flow telemetry query. It lacks an explicit action verb (e.g. 'fetch panel rows'), but the domain is clearly disjoint from every sibling tool.

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?

It enumerates the panel families (uniswapx_evals_{chain}, uniswapx_shadow_{chain}, uniswapx_realizability) and the four supported chains, which implies selection logic, and it states the access/payment conditions. However it never says when to pick this over another source, what distinguishes shadow from evals, or which panel answers which question.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources