Skip to main content
Glama

CryptoData API

by io.github.elevasyncsolutions-jpg
OverviewDiscussionsAdmin

get_top_losers

Top 24h losers (api_key required).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
api_keyNoYour API key from register()

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / api_key / description
      Previous value: -"Optional — for billing"New value: +"Your API key from register()"
  2. Changed2 schema fields changed
    • addedInput schema / properties / api_key / description
      Added value: +"Optional — for billing"
    • changedInput schema / required
      Previous value: -[
-  "api_key"
-]New value: +[]
  3. Changed1 schema field changed
    • removedInput schema / properties / api_key / description
      Removed value: -"Your API key"
  4. First observed

TDQS

C2.6/5.0
Behavior2/5

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

No annotations provided, so description must cover behavioral traits. Only discloses api_key requirement. Does not mention that it is a read-only operation, rate limits, data freshness, or response format.

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?

Description is very short and to the point. No fluff, but could be slightly improved by front-loading the action verb.

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

Completeness2/5

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

Given no annotations, no output schema, and 2 parameters, the description is too minimal. It lacks details on what constitutes a 'loser' (percentage change?), exact timeframe (last 24 hours from now?), sorting, or pagination behavior.

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

Parameters1/5

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

Description states 'api_key required' but schema marks api_key as optional (required: []). This contradiction adds incorrect information. Description does not explain the limit parameter, which is undocumented in 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?

Description states 'Top 24h losers' which clearly indicates the resource (24-hour losers) and timeframe. The name includes 'get', making the action implicit. It is clear but lacks an explicit verb like 'list' or 'retrieve'.

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?

No guidance on when to use this tool versus siblings like get_top_gainers or get_top. Only mentions api_key required, which is a prerequisite, not usage context.

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

All CryptoData API 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