Skip to main content
Glama

trending

Identify which cryptocurrencies are trending by analyzing real-time search and trading activity.

Instructions

Get trending cryptocurrencies right now — what people are searching for and trading.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The getTrending() function fetches trending cryptocurrencies from CoinGecko's /search/trending API and returns an array of coins with name, symbol, market_cap_rank, and price_btc.
    async function getTrending() {
      const data = await fetch('https://api.coingecko.com/api/v3/search/trending');
      return {
        coins: data.coins.map(c => ({
          name: c.item.name,
          symbol: c.item.symbol,
          market_cap_rank: c.item.market_cap_rank,
          price_btc: c.item.price_btc,
        })),
      };
    }
  • Tool definition/schema for the 'trending' tool: accepts no input parameters and returns trending cryptocurrencies.
    {
      name: 'trending',
      description: 'Get trending cryptocurrencies right now — what people are searching for and trading.',
      inputSchema: { type: 'object', properties: {} }
  • index.js:332-333 (registration)
    The switch-case handler in handleToolCall() that dispatches 'trending' calls to getTrending().
    case 'trending':
      return await getTrending();
  • The fetch() helper used by getTrending() to make HTTP requests to the CoinGecko API.
    function fetch(url) {
      return new Promise((resolve, reject) => {
        const req = https.get(url, { headers: { 'User-Agent': 'mcp-market-data/0.1' } }, (res) => {
          let data = '';
          res.on('data', chunk => data += chunk);
          res.on('end', () => {
            try { resolve(JSON.parse(data)); }
            catch (e) { reject(new Error(`Parse error: ${data.slice(0, 200)}`)); }
          });
        });
        req.on('error', reject);
        req.setTimeout(15000, () => { req.destroy(); reject(new Error('Timeout')); });
      });
    }
Behavior2/5

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

No annotations are provided, so the description must fully disclose behavioral traits. It only states the basic function without revealing any side effects, authentication needs, rate limits, or data freshness, which is insufficient for a tool with no annotation coverage.

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, well-formed sentence that conveys the tool's purpose without any redundant or extraneous words. Every word contributes to clarity.

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?

Given the simplicity (0 parameters, no annotations, no output schema), the description provides the essential purpose but lacks any additional context about output format, update frequency, or limitations. This may be sufficient for a trivial tool but offers minimal information beyond the name.

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?

The input schema has zero parameters, so schema coverage is 100% and the baseline is 4. The description adds no parameter information, but none is needed.

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 clearly states the verb 'Get' and the resource 'trending cryptocurrencies', specifying the temporal scope ('right now') and the data sources ('searching and trading'), which effectively distinguishes it from sibling tools like price, market_cap, and analyze.

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?

The description provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites, context, or when not to use it, leaving the agent without decision-making support for tool selection.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ShipItAndPray/mcp-market-data'

If you have feedback or need assistance with the MCP directory API, please join our Discord server