Skip to main content
Glama

Crypto Coins

ListCryptoAssets
Read-only

List the crypto coins with prices, in symbol order: symbol, pair, whether it still trades and its first stored trade date. Coins are known by symbol only (BTC, ETH); there are no coin names, market caps or supplies. query keeps the symbols that start with it. Prices are in US dollars from one exchange. Use GetCryptoQuote for the latest price, GetCryptoPrices for daily candles and GetCryptoIntradayPrices for candles within the day. Included on every plan.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ListCryptoAssets"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoStart of a coin symbol, e.g. BT (default: every coin)
offsetNoCoins to skip, for the next page (default: 0)
maxResultsNoMaximum coins to return (default: 100, max: 500)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely non-structured context: the entity model is symbol-only, prices come from a single exchange in USD, and the endpoint is available on every plan (entitlement). It does not discuss paging behavior beyond what the schema documents, which keeps it just short of a 5.

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?

Content is front-loaded: returned fields first, then entity model, then filter semantics, then sibling routing, then availability. Every clause carries information, though the opening sentence is long enough that a small amount of decoding is required.

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?

With three fully documented optional parameters, annotations covering the safety profile, and no output schema, the description supplies everything needed to call the tool correctly: field list, filter behavior, currency and source of prices, and routing to price-candle siblings.

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, but the description adds real semantics by stating that 'query keeps the symbols that start with it' — clarifying prefix matching rather than substring matching. It also notes the default returns every coin, reinforcing the query parameter's default value.

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 opens with a specific verb and resource ('List the crypto coins with prices, in symbol order') and enumerates the returned fields: symbol, pair, trading status, first stored trade date. It also states what the resource is NOT (no coin names, market caps or supplies), which lets an agent distinguish it from price/quote tools without opening a schema.

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?

It explicitly routes the agent to the alternatives by condition: GetCryptoQuote for the latest price, GetCryptoPrices for daily candles, GetCryptoIntradayPrices for intraday candles. That is a direct when-to-use-this-vs-siblings statement rather than an implied one.

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.