Sausage Onchain

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.9/5.0

Behavior5/5

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

No annotations are provided, so the description carries the full burden. It discloses the paid nature, the need for signed x402 payment, the use of Chainlink's latestRoundData, and that cross-conversion reports both legs. This goes beyond mere 'get price' and explains the operational behavior and prerequisites.

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 three sentences, front-loading the core purpose first, then explaining optional conversion and the payment flow. Every sentence contributes unique, actionable information with no fluff.

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?

Given the complexity (paid, multi-step, cross-conversion) and lack of output schema or annotations, the description is remarkably complete. It covers the data source (Chainlink), the payment mechanism, the cross-conversion behavior, and directs to the alternative pricing tool. It sufficiently sets expectations for the return, mentioning 'round metadata' and 'both legs reported'.

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 description coverage is 100%, so the baseline is 3. The description adds value for `to` (cross-convert via USD feeds, both legs reported) and clarifies the x_payment flow, but the schema already explains these parameters in detail. The extra context pushes it slightly above baseline.

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 clearly states the tool's function: 'Live Chainlink on-chain spot price for an asset (latestRoundData, with round metadata)'. It also distinguishes from the sibling 'pricing' tool by noting that the free `pricing` tool lists every price at once, making the purpose specific and non-duplicative.

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?

The description provides explicit usage guidance, including the two-step payment process ('call without x_payment to receive this call's exact terms... then call again with x_payment') and directs to the free `pricing` tool for a bulk price list. It also references /prices/feeds for listing available feeds, clarifying when to use this tool versus alternatives.

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

All Sausage Onchain 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.2/5.0

Disambiguation5/5

Each tool has a clear, distinct purpose: address screening, chain info, ENS resolution, data discovery, gas routing, gas pricing, NFT scam checking, pricing metadata, data requests, spot prices, swap quotes, and token safety. Although gas_compare and gas_price both involve gas, one ranks chains while the other gives fees for a single chain; token_safety and nft_scam_check target different asset types. No two tools are likely to be confused.

Naming Consistency2/5

Names are all lowercase snake_case but follow no single convention. Some are verb-first (find_data, request_data, swap_quote), some noun-first with a verb (address_screen, ens_resolve, gas_compare), and several are noun-noun compounds (chain_info, gas_price, spot_price, token_safety). This mixed pattern makes the naming feel inconsistent, even though each name is readable.

Tool Count5/5

With 12 tools, the server sits comfortably in the well-scoped range for a blockchain data/utility provider. Each tool addresses a distinct need, and the count is not excessive for the breadth of on-chain operations covered. Every tool appears to earn its place without redundancy.

Completeness4/5

The tool surface covers a broad set of on-chain needs: screening (address, token, NFT), pricing (spot, swap, gas), identity (ENS), chain metadata, and meta-tools for discovery and requests. Minor gaps exist, such as no direct transaction/block inspection or portfolio-level functions, but these are not core to the server's apparent purpose and agents can work around them using find_data to locate additional endpoints.

Resources

Need Help?