Skip to main content
Glama
Sign In

Realtap

by io.github.CSteenkamp
OverviewDiscussionsAdmin

Prices of several tokens

get_token_prices
Read-onlyIdempotent

Prices of up to 100 Cardano tokens in one call (ADA and USD per token), optionally with the change of the ADA price over windows from 5 minutes to 90 days (percent). Use it instead of calling get_token repeatedly when you hold a list of units. A null change means the token did not trade yet at the start of that window; 30d and 90d only reach back as far as our history. Prices come from DEX pools: check liquidity with get_token before quoting a thin token.

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": {
      "units": "<units>"
    },
    "name": "get_token_prices"
  }
}

Input Schema

NameRequiredDescriptionDefault
unitsYesComma separated token units (56-hex policy id + asset name in hex; "lovelace" for ADA), 1 to 100 of them. Get them from `search` or `list_tokens`.
windowsNoOptional comma separated windows for the price change: 5m, 1h, 6h, 24h, 7d, 30d, 90d.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Goes well beyond the readOnly/idempotent annotations: discloses data provenance (DEX pools), the null-change semantics, and the hard history limit that 30d/90d only reach as far back as the index covers. These are exactly the gotchas an agent would otherwise misread as missing data.

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?

Dense, front-loaded, and each sentence carries distinct information (scope, alternative, null semantics, history limit, liquidity caveat). Slightly packed into two long sentences, but nothing is redundant.

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?

No output schema exists, yet the description still specifies the return shape (ADA and USD per token, percent change over windows) and the edge cases (null change, history depth). An agent has everything needed to call and interpret it correctly.

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%, so the baseline is 3, but the description adds real interpretive value: it frames the token cap ('up to 100'), the window range ('5 minutes to 90 days'), and explains what a null change value means for the `windows` parameter's output — the kind of meaning the schema cannot express.

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?

States a specific verb+resource plus scope: 'Prices of up to 100 Cardano tokens in one call (ADA and USD per token)', with optional change windows. It is unambiguously the batch price tool versus the single-token get_token and the historical get_token_candles.

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?

Explicit routing rule: 'Use it instead of calling `get_token` repeatedly when you hold a list of units', plus a pre-condition ('check liquidity with `get_token` before quoting a thin token'). Both the when-to-use and the when-to-defer-to-a-sibling are named.

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

All Realtap toolsInspect
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