Skip to main content
Glama
1tylermitchell

Sairen

by 1tylermitchell
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

get_dex_spot_price

Retrieve live spot prices, liquidity depth, and tick state for Base L2 pairs by querying Uniswap v3 and Aerodrome pools directly, avoiding stale aggregator data.

Instructions

    [Cost: $0.001 USDC on Base & Solana] Direct on-chain spot price, liquidity depth, and tick state oracle for Base L2.
    Queries live smart contract pools directly (Uniswap v3 and Aerodrome) without relying on centralized aggregators (CoinGecko) or stale off-chain indexers.
    Returns exact pool contract addresses, fee tiers, current block height, active liquidity reserves, and sqrtPriceX96 tick states.
    Supported pairs: WETH-USDC, cbBTC-USDC, AERO-USDC.

    Args:
        pair: Target trading pair symbol (default: 'WETH-USDC', also supports 'cbBTC-USDC', 'AERO-USDC').
        payment_signature: Optional x402 Base USDC transaction hash or developer mock key.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pairNoWETH-USDC
payment_signatureNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the transparency burden and does disclose cost, direct smart-contract querying, returned fields, and supported pairs. It does not fully explain payment failure modes or read-only status, but it covers the important operational 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?

The description is dense but efficient: cost, purpose, mechanism, outputs, supported pairs, and parameters are covered in a compact form. The Args section repeats schema information but earns its place by adding value.

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 oracle with no output schema, it lists key return values and supported pairs, which is fairly complete for selection and invocation. It omits response format details and clearer payment_signature guidance, and the 'Base & Solana' cost line creates slight ambiguity, but these are gaps rather than blockers.

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 0%, so the description's Args section is essential and it compensates: pair gets explicit default and accepted values, payment_signature gets optionality and accepted forms. The payment_signature explanation remains slightly vague (what x402 hash/mock key means), but it adds meaning beyond the bare schema.

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

Purpose5/5

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

Description uses specific verb+resource: direct on-chain spot price, liquidity depth, and tick state oracle for Base L2. It names exact pools, return fields, and supported pairs, and the 'Base L2' scope separates it from the Solana sibling get_solana_dex_price.

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 states when to use: when live on-chain pool data is needed instead of centralized aggregators or stale indexers. It does not explicitly name alternative tools or list exclusions, but the Base L2 scope and supported pairs give clear context.

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

Deploy Server

Other Tools