Skip to main content
Glama
nad33mahm3d

mcp-crypto-toolkit

by nad33mahm3d

trending

Identify which coins are gaining attention by fetching CoinGecko's hot coins list and the Crypto Fear & Greed Index to gauge market sentiment.

Instructions

What's hot right now: CoinGecko trending coins plus Crypto Fear & Greed Index.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
include_fear_greedNoInclude Alternative.me Fear & Greed Index (default true)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

B3.3/5.0
Behavior3/5

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

The description discloses the main output contents: CoinGecko trending coins and the Alternative.me Fear & Greed Index. With no annotations, the description must carry the behavioral transparency burden, but it does not mention output shape, pagination, freshness, or any side-effect profile, leaving notable gaps.

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?

The description is a single front-loaded sentence with no wasted words. It efficiently conveys the current-trend context and the exact payload sources in a compact, scannable form.

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 tool with one optional parameter, this is close to sufficient, but there is no output schema and no annotation context, so the description should specify more about the response shape or how include_fear_greed changes the result. It states the broad contents but leaves ambiguity about what 'trending coins' actually returns.

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 include_fear_greed parameter is already fully documented. The description only reinforces that the Fear & Greed Index is part of the result and does not clarify parameter effects or add meaningful semantic detail 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 clearly identifies the resource: CoinGecko trending coins plus the Crypto Fear & Greed Index, and 'What's hot right now' signals a current-market snapshot. However, it lacks an explicit verb like 'get' or 'list' and does not explicitly distinguish itself from siblings such as top_coins.

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 is provided about when to use this tool versus alternatives like top_coins or get_price. The phrase 'What's hot right now' implies a current-trend use case, but there are no explicit exclusions, prerequisites, or comparisons to sibling tools.

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