Skip to main content
Glama

quote_anansi

Live, read-only swap quotes for ANANSI on Base (Uniswap v3 ANANSI/WETH 0.3%) for $5/$20/$50: price impact from QuoterV2, pool liquidity, Uniswap link, and a plain risk warning. ANANSI is not an investment; credits can also be bought with USDC.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It does disclose the safety-relevant facts (read-only, live, QuoterV2 as the price source, fixed quote denominations) plus a risk warning, but says nothing about refresh/caching behavior, rate limits, freshness guarantees, or failure modes when the pool is illiquid.

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?

Two sentences, front-loaded with the core capability, with the venue/pool parenthetical supplying necessary precision. The final clause about ANANSI not being an investment and USDC credits is slightly tangential marketing copy but does carry a risk disclaimer.

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?

With no output schema and no annotations, the description properly enumerates what a caller receives: price impact, pool liquidity, a Uniswap link, and a risk warning. That is adequate for a zero-parameter read-only tool, though it omits any notion of quote staleness or execution caveats.

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?

The tool takes zero parameters, which is the baseline-4 case. The description usefully confirms the denominations are fixed ($5/$20/$50) rather than agent-supplied, removing any ambiguity about whether input is expected.

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 gives a specific verb and resource (live read-only swap quotes) and pins down the exact venue, chain and pool (Uniswap v3 ANANSI/WETH 0.3% on Base), which is far more than the bare name conveys. It does not explicitly contrast itself with the related sibling topup_quote, so it falls short of the 5 tier.

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?

Usage is implied rather than stated: an agent can infer it should call this to inspect ANANSI swap pricing at the fixed $5/$20/$50 tiers, and the closing line hints USDC credit purchases are a separate path. There is no explicit when-not guidance or pointer to the alternative tool (e.g. topup_quote) for actually executing a purchase.

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.