Skip to main content
Glama

oracle_staleness

Read-onlyIdempotent

Is this V3 pool's TWAP oracle current — or will observe() revert? — Screen a Uniswap-V3-style pool before trusting its TWAP oracle: reads slot0 cardinality + the newest observation, anchors now to Base BaseTime (timestampMs), and returns healthy / shallow / stale / unusable. Catches a STALE observation (wrong TWAP window) and a SHALLOW buffer (observe reverts OLD on a real lookback). Sharper post-Denim: 200ms blocks burn a fixed cardinality ~10x faster. Pure onchain reads; an unreadable pool is UNKNOWN, not safe. Required input: pool. Priced $0.03 per call over x402 on Base; send a prepaid x-credit-token header for unlimited calls, or get 1 free call/day per tool. No API key required.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "pool": "<pool>"
    },
    "name": "oracle_staleness"
  }
}

Input Schema

NameRequiredDescriptionDefault
poolYesUniswap-V3-style pool address

Output Schema

NameRequiredDescriptionDefault
dataNoThe result payload. Shape is service-specific; every field is documented in the tool description.
serviceNoThe service id that answered.
checkedAtNoISO-8601 timestamp of when the underlying reads were taken.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Beyond the annotations it discloses the four-state return contract, the critical failure semantics ('an unreadable pool is UNKNOWN, not safe'), the post-Denim cardinality decay behavior, and the payment/auth model (x402 pricing, prepaid header, free tier, no API key). 'Pure onchain reads' partly restates readOnlyHint, but the UNKNOWN-is-not-safe warning and auth details add real value.

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 core question and the return states are front-loaded, and the pricing/auth details are clustered at the end where they belong. Some phrasing is promotional ('Sharper post-Denim') and the payment sentence is dense, but nothing is wasted outright.

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?

For a single-parameter, read-only check with an output schema, the description covers everything an agent needs: what is measured, what the result states mean, how unreadable pools are handled, and how access/pricing works. Return-value detail is correctly left to the output schema.

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?

There is a single parameter with 100% schema coverage, so the schema already carries the semantics; the description only restates it as 'Required input: pool' and adds that it is a Uniswap-V3-style pool address. Baseline 3 applies when the schema does the heavy lifting.

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?

The description leads with a specific question the tool answers (is this V3 pool's TWAP oracle current, or will observe() revert) and then names the exact mechanism: reads slot0 cardinality plus the newest observation and returns healthy/shallow/stale/unusable. This is a concrete verb-plus-resource statement that no sibling tool covers.

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 gives a clear trigger — 'Screen a Uniswap-V3-style pool before trusting its TWAP oracle' — which tells the agent exactly the decision context. It stops short of naming an alternative or an explicit when-not-to-use case, but the applicability is unambiguous.

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