SiteCheck Crypto & Finance

Chainlink on-chain price feed: latest round answer in USD

crypto_chainlink_price_feeds

Read-only

Chainlink on-chain price feed (ETH/USD or BTC/USD, Ethereum mainnet): latest round answer in USD, round id, and the start and update times with the age of the last update in seconds. Only the two feeds listed here are supported. Heartbeat and deviation thresholds are not reported. Related tools on this server, for a different need: crypto_tao_alpha_price_history when you need historical price trajectory, pool liquidity, and reserve. 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_chainlink_price_feeds"
  }
}

Input Schema

Name	Required	Description	Default
`feed`	No	eth-usd or btc-usd (default eth-usd)

Output Schema

Name	Required	Description	Default
`feed`	No
`pair`	No
`source`	No
`roundId`	No
`decimals`	No
`answerUsd`	No
`checkedAt`	No
`startedAt`	No
`updatedAt`	No
`ageSeconds`	No
`aggregator`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Beyond the readOnly/openWorld annotations, it discloses that heartbeat and deviation thresholds are NOT reported, that only two feeds exist, and that each successful call costs $0.002 via x402 while failed calls are free. Those are exactly the behavioral facts an agent needs before invoking a paid read.

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?

Content is front-loaded with what is returned, then constraints, then the alternative and pricing. It is efficient, though the pricing/related-tools tail could be tightened without losing meaning.

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?

Returned fields, supported feed domain, cost and payment rails, and explicit non-reported metrics are all covered; an output schema already exists so return shape needn't be re-explained. Nothing material for correct invocation is 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?

Schema coverage is 100% and the schema already documents 'eth-usd or btc-usd (default eth-usd)'. The description reinforces the valid domain by naming the two supported feeds and stressing no others are offered, adding slight meaning over the raw 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?

The description states a specific verb and resource ('Chainlink on-chain price feed'), fixes the scope ('ETH/USD or BTC/USD, Ethereum mainnet'), and enumerates exactly what is returned (latest round answer in USD, round id, start/update times, age). An agent can distinguish this from the large sibling set without opening the schema.

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 explicitly bounds usage ('Only the two feeds listed here are supported') and names a sibling to use for a different need (crypto_tao_alpha_price_history for historical trajectory). It lacks an explicit when-not statement for the broader set of spot-price siblings, but the context it gives is clear.

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?