Skip to main content
Glama

FinanceQuery

Top Cryptocurrencies

get_crypto
Read-onlyIdempotent

Get top cryptocurrency coins by market cap from CoinGecko (no API key required).

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

Input Schema

NameRequiredDescriptionDefault
countNoNumber of top coins to return (default: 50, max: 250)
limitNoMaximum coins per page; omitted = curated default (25)
cursorNoOpaque continuation token from a previous response's `pageInfo.endCursor`; omitted = first page
fieldsNoComma-separated list of GraphQL field names to include; omitted = all fields
vs_currencyNoQuote currency (default: usd)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, open-world and non-destructive, so the safety profile is covered. The description adds two genuinely useful facts beyond that: results are ordered by market cap and no authentication/API key is needed. It says nothing about rate limits, result freshness, or pagination behavior, which are the remaining unknowns for an open-world data fetch.

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?

A single sentence with no filler, and the most important fact (what is returned and how it is ordered) is front-loaded. It is efficient, though so terse that it omits any connective guidance an agent would find useful.

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

Completeness4/5

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

For a zero-required-parameter read tool with full schema coverage and a complete annotation set, the description covers purpose, source and ranking adequately. Missing are only secondary details like whether market-cap ordering is stable and how the cursor interacts with limit, which the schema partly implies.

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 coverage is 100%, so count, limit, cursor, fields and vs_currency are all documented in structured data, including defaults and max values. The description adds no additional parameter meaning, which is acceptable given the schema does the work, so the baseline of 3 applies.

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?

States a specific verb and resource ('Get top cryptocurrency coins') plus the ranking criterion ('by market cap') and the upstream source (CoinGecko). An agent can distinguish it from get_crypto_news or get_forex on domain alone, though the description never explicitly contrasts with a 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 by 'top ... by market cap', which signals a ranked-listing use case, and the 'no API key required' note removes a common setup concern. It gives no when-not-to-use guidance, no mention of when to prefer a news or chart tool instead, and no exclusions.

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.