SiteCheck Crypto & Finance

Lido stETH vs ETH peg from public USD prices: stETH and ETH

crypto_lido_steth_peg

Read-only

Lido stETH vs ETH peg from public USD prices (DefiLlama coins API): stETH and ETH price, discount or premium in %, plus Lido's total stETH staked and market cap. The two prices can be quoted a few minutes apart. Curve pool balances and the Lido withdrawal queue are not included. Price: $0.002 in USDC per successful call, paid with x402 (Base, Solana or Arc); failed calls are not charged.

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

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`ethUsd`	No
`pegPct`	No
`source`	No
`stethUsd`	No
`checkedAt`	No
`pricesQuotedAt`	No
`stethTotalStaked`	No
`stethMarketCapUsd`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Beyond readOnlyHint and openWorldHint, it discloses the paid x402 model, exact cost, supported networks, and that failed calls are free. It also adds useful data-quality caveats about quote timing and missing sources, which are not captured by annotations.

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?

The description is front-loaded and compact: purpose, source, fields, caveats, exclusions, and pricing each appear once. The only minor redundancy is repeating the title phrase, but no sentence is wasted.

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?

With an output schema present and no parameters, the description supplies the remaining context an agent needs: data source, timing caveat, exclusions, and payment terms. No critical invocation detail appears to be missing.

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?

There are zero parameters, so parameter semantics are not required; the rubric baseline is 4. The description adds no parameter meaning, but none exists to clarify.

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 names the exact comparison (Lido stETH vs ETH peg), the data source (DefiLlama public USD prices), and the returned measures (prices, discount/premium, total stETH staked, market cap). This is specific enough to distinguish it from generic price-feed siblings, even though those alternatives are not named.

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 defines scope and exclusions, noting that Curve pool balances and the Lido withdrawal queue are not included, and warns that the two prices may be quoted minutes apart. It does not explicitly name alternative tools or state when to choose this over a sibling, so routing guidance is only implied.

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

All SiteCheck Crypto & Finance tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?