Skip to main content
Glama
@caelaralabs/mcp

@caelaralabs/mcp

caelara_crypto_token_price_aggregator

Fetch the median USD price for a crypto ticker across Coinbase, Kraken and Bitstamp with bid-ask spread, and add on-chain pool pricing when a token contract address is provided.

Instructions

[On-Chain Intelligence] Median USD price for a ticker across Coinbase, Kraken and Bitstamp with spread, plus on-chain pool price when a contract address is supplied Measured p50 12 ms, p95 14 ms (2026-11-21, benchmarks.caelaralabs.com). Calls https://crypto.caelaralabs.com.

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": {
      "symbol": "<symbol>"
    },
    "name": "caelara_crypto_token_price_aggregator"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYesTicker, e.g. ETH, BTC, SOL
addressNoOptional token contract/mint for on-chain pool pricing

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and does disclose useful behavior: the three named exchange sources, that the reported figure is a median rather than a single quote, that spread is included, and that a pool price is added when an address is given. It omits authentication requirements, rate limits, failure behavior, and any hint at how stale prices or divergences are handled.

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?

The core capability is front-loaded in the first sentence, with the conditional behavior attached immediately after. The benchmark latency figure and endpoint URL are somewhat promotional padding that does not help an agent decide or invoke, but they are brief and do not bury the substance.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter read tool with no annotations and no output schema, the description gives a reasonable sketch of returned values (median, spread, pool price) and the source set. It remains incomplete on return structure, error conditions, and access requirements, which matter here precisely because no output schema or annotations exist to fill the gap.

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 goes slightly further by clarifying that the address parameter changes the response shape (an additional on-chain pool price is returned), which is more than the schema's bare 'optional token contract/mint' note conveys. It adds no format examples beyond the schema's ticker example.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/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: a median USD price for a ticker aggregated across Coinbase, Kraken and Bitstamp, with spread, and an added on-chain pool price. It is clearly not the same as sibling tools like the safety composite or liquidity depth tool. It stops short of a 5 because it never explicitly names or rules out a sibling alternative.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to prefer this over the other crypto tools (e.g. liquidity depth, stablecoin depeg monitor) or when not to use it. The only conditional language, 'when a contract address is supplied', describes a parameter effect rather than a usage decision, so the agent must infer the calling context.

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

Deploy Server

Other Tools