Skip to main content
Glama

Sato Hub: Build Onchain & Crypto Agents

Compare the Uniswap pools for a pair, with the evidence and the gap named

onchain_agent_route_lp
Read-onlyIdempotent

USE WHEN an agent is deciding which Uniswap pool and fee tier to provide liquidity to for a pair Sato Route already quotes, and wants the observed readings rather than an opinion. NOT FOR a swap (use onchain_agent_route_swap or onchain_agent_swap instead) or a token launch (use onchain_agent_route_launch).

RETURNS every v3 pool the weekly LP lane found across the four standard fee tiers, each with its in-range liquidity, the swaps and volume actually counted, the window that count covered, and a fee-revenue proxy.

RULE ENFORCED: a route is a RECOMMENDATION. chosen_by names every field the pick was made on and where each was read. THE LARGEST TERM IS MISSING ON PURPOSE: impermanent loss is not modelled, not approximated and not bounded, and it appears in chosen_by as an explicit null rather than being quietly omitted. A fee-revenue figure here is a PROXY — the pool's published fee rate multiplied by volume we counted, in token0's own units — and is never called revenue, an APR or a yield. Readings are never scaled up from the window covered to a full week.

THE PICK: highest observed fee-revenue proxy per day per unit of in-range liquidity, among pools whose window could be read. When nothing is rankable the answer is chosen: null with a reason per pool, never a low-confidence pick.

COVERAGE: Uniswap v3 on Base and Ethereum, for the pairs the router quotes. Uniswap v4 rows come back null WITH THEIR REASON — v4 is a singleton PoolManager and publishes no per-pair pool id — and null is unknown, never zero. Every non-Uniswap venue is outside the reading entirely.

NON-CUSTODIAL: this tool never signs, holds, moves or provides liquidity, and nothing it returns is advice.

RETURNS (json): { chain, pair, week, latest_week?, note?, pools: [{ venue, pool, fee_tier_ppm, fee_tier_pct, liquidity, swaps_observed, volume_token0_observed, fee_revenue_proxy, fee_revenue_proxy_per_day, proxy_per_day_per_liquidity, token0, token1, covered_days, window_days, window_complete, method, evidence_tier, caveat, as_of, unknown_reason }], chosen: { pool, venue, fee_tier_ppm, because, chosen_by } | null, unranked, as_of, checked_at, caveat, rules }; latest_week and note appear only when the latest week held no reading for the pair and week is the newest week that does. When the pair is not collected: { unavailable, supported, checked_at, caveat }.

Example: { chain: "Base", pair: "WETH-USDC" }

Input Schema

NameRequiredDescriptionDefault
pairYesThe pair, either way round: 'WETH-USDC', 'usdc/weth', 'WBTC_WETH'. Only the pairs Sato Route quotes are collected.
chainYesChain the pool is on. Collected: Base, Ethereum. Anything else answers `unavailable` with the covered list — unknown, never an empty result presented as none.
response_formatNoText format; structuredContent is JSON either way.markdown

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Changed1 schema field changed
    • changedInput schema / properties / response_format / description
      Previous value: -"Output format: 'markdown' (default) or 'json'."New value: +"Text format; structuredContent is JSON either way."
  3. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, openWorld, non-destructive), yet the description adds substantial behavioral context beyond them: the recommendation-vs-fact rule, the deliberate omission of impermanent loss surfaced as an explicit null, the fee-revenue proxy definition, the 'never scaled up' window rule, the null-means-unknown (not zero) semantics, v4 null-with-reason handling, and a non-custodial statement. This is rich disclosure beyond structured fields.

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?

Front-loaded with USE WHEN / NOT FOR and organized under clear headers (RULE, THE PICK, COVERAGE, NON-CUSTODIAL, RETURNS). Given the tool's complexity the length is mostly justified, but the emphatic guardrail phrasing ('never... never...') and the long field enumeration in the RETURNS block are more verbose than strictly needed.

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

Completeness5/5

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

No output schema exists, so the description must carry the return contract, and it does thoroughly: the full pools[] field list, the chosen object with chosen_by, the unranked case, the latest_week/note fallback, and the unavailable shape. Combined with the pick rule and coverage limits, an agent has everything needed to call and interpret this complex tool.

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 both required params (pair, chain) and the response_format enum are already fully documented, including the 'unknown, never empty' semantics for unsupported chains/pairs. The description only restates coverage constraints and adds a one-line example, so the schema does the heavy lifting — baseline 3 applies.

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?

States a specific verb and resource: comparing Uniswap v3 pools/fee tiers for a pair so an agent can decide where to provide liquidity. It explicitly distinguishes itself from onchain_agent_route_swap, onchain_agent_swap and onchain_agent_route_launch, so the agent can route correctly without opening any schema.

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

Usage Guidelines5/5

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

Opens with an explicit 'USE WHEN' condition (deciding which pool/fee tier to LP, wanting observed readings not an opinion) and a 'NOT FOR' clause naming the three alternative tools for swaps and launches. When-to-use, when-not, and alternatives are all present.

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.