Skip to main content
Glama

token_price_aggregator

Median USD price for a ticker across Coinbase, Kraken and Bitstamp with spread, plus DEX price when a contract address is supplied

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": "token_price_aggregator"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYesTicker, e.g. ETH, BTC, SOL
addressNoOptional token contract/mint for DEX pricing

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, and it only discloses the aggregation method (median) and the source exchanges. It says nothing about whether results are cached, what happens when one venue fails or a ticker is unsupported, whether the DEX leg is optional/skipped or errors, or how outdated a quote may be. Nothing in it contradicts expectations, but key reliability context for a pricing tool is absent.

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?

A single front-loaded sentence that names the output (median USD price plus spread), the sources, and the conditional addition. There is no filler, and the optional-address condition is placed where it matters most.

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 output schema, the description covers what is computed and where the data comes from, which is the core need. It leaves the return shape of the spread value and the partial-failure/best-effort behavior unaddressed, so an agent cannot fully predict the response. Adequate but with clear gaps for a price-aggregation tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already explains both symbol and address, making 3 the baseline. The description adds marginal meaning by tying the address parameter to DEX pricing and the symbol-only case to CEX aggregation, but it adds no format, casing, or chain-qualification guidance beyond the schema.

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 computation and sources: a median USD price for a ticker aggregated across Coinbase, Kraken and Bitstamp, plus spread, and a DEX price when a contract address is given. That is far more than a restatement of the name and lets an agent tell it apart from data-inspection siblings like dex_liquidity_depth or base_erc20_inspector. It stops short of 5 only because it doesn't explicitly contrast itself with any named sibling.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: the agent can infer this fetches a reference price and that supplying an address enables DEX pricing in addition to CEX pricing. There is no explicit when-to-use, when-not-to-use, or pointer to alternatives such as dex_liquidity_depth when depth rather than price is needed. A caller must infer the conditions from the phrasing alone.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources