Professor Sausages — On-chain

Oracle spot price

spot_price

Live Chainlink on-chain spot price for an asset (latestRoundData, with round metadata). Pass to as well to cross-convert two assets via their USD feeds, with both legs reported. Paid: call without x_payment to receive this call's exact terms (amount, asset, network), sign them, then call again with x_payment. The free pricing tool lists every price at once.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`to`	No	Optional second asset — converts `asset` into it instead of quoting USD.
`asset`	Yes	Asset symbol with a Chainlink feed (call /prices/feeds free to list them).
`chain`	No	Which chain's oracle to read.	base
`amount`	No	Amount to convert (with `to`).
`x_payment`	No	Optional signed x402 payment payload (base64, what the X-PAYMENT header carries). Omit to receive the exact payment terms; sign them (e.g. @x402/fetch) and call again with this argument to settle and get the data.

TDQS

A4.6/5.0

Behavior4/5

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

No annotations, but the description discloses the paid two-step workflow, the on-chain oracle read, and that cross-conversion reports both legs. It does not mention rate limits or output structure in detail, but the payment behavior is well covered.

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?

Three dense, information-packed sentences with the main purpose front-loaded. No wasted words; the structure flows naturally from core function to advanced features to alternatives.

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?

The tool is complex due to payment terms and cross-conversion, and the description addresses both adequately. Given no output schema, mentioning latestRoundData and round metadata sets expectations for return values.

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 covers all parameters, so baseline is 3. The description adds meaning beyond schema by explaining cross-conversion via USD feeds with both legs reported, and by clarifying the payment flow for x_payment and asset.

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?

Description clearly states it returns live Chainlink spot price via latestRoundData, with round metadata. The cross-conversion behavior and explicit distinction from the free `pricing` tool make the purpose unmistakable.

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?

Explicitly contrasts with the free `pricing` tool and explains the two-step paid flow (call without x_payment for terms, then with x_payment). This gives clear when-to-use and when-not-to-use guidance.

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

All Professor Sausages — On-chain tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0

Disambiguation5/5

Each tool targets a distinct concern: screening, chain metadata, ENS resolution, gas estimation, asset pricing, swap quoting, token safety, NFT scam detection, pricing catalog, and data discovery/request. Overlapping terms like 'price' or 'check' are clearly separated by modifiers and descriptions, leaving no ambiguity about which tool to select.

Naming Consistency4/5

All tool names use lowercase snake_case and a consistent style, but the pattern mixes verb_noun (find_data, request_data) with noun_noun or noun_verb (chain_info, spot_price, gas_compare). This is a minor deviation; the naming remains predictable and readable.

Tool Count5/5

Twelve tools is well-scoped for a multi-purpose on-chain data and security server, fitting comfortably in the 3-15 ideal range. Each tool earns its place, covering distinct operations without redundancies.

Completeness4/5

The server covers a broad set of on-chain utilities: address screening, chain info, ENS, gas (both single-chain and comparative), spot prices, swap quotes, token/NFT safety, and pricing discovery. Notable gaps like on-chain balances or transaction sending are missing, but the 'find_data' and 'request_data' tools mitigate these by letting users discover and request additional endpoints.

Resources

Need Help?