Skip to main content
Glama

compare

Compare multiple cryptocurrency assets side by side to analyze prices, price changes, and market capitalizations in real-time.

Instructions

Compare multiple assets side by side — prices, changes, market caps.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolsYesComma-separated symbols (e.g., "BTC,ETH,SOL")

Implementation Reference

  • Handler implementation for the 'compare' tool, which iterates through provided symbols and fetches their prices.
    case 'compare': {
      const symbols = args.symbols.split(',').map(s => s.trim());
      const results = [];
      for (const sym of symbols.slice(0, 10)) {
        try {
          const p = await getCryptoPrice(sym);
          results.push(p);
        } catch (e) {
          results.push({ symbol: sym, error: e.message });
        }
      }
      return results;
    }
  • Schema definition for the 'compare' tool, specifying input 'symbols' as a required string.
      name: 'compare',
      description: 'Compare multiple assets side by side — prices, changes, market caps.',
      inputSchema: {
        type: 'object',
        properties: {
          symbols: { type: 'string', description: 'Comma-separated symbols (e.g., "BTC,ETH,SOL")' }
        },
        required: ['symbols']
      }
    },
Behavior3/5

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

With no annotations provided, the description carries the full burden of disclosure. It enumerates what data is compared (prices, changes, market caps), giving insight into the tool's scope, but omits whether data is real-time, any rate limits, or what format the comparison output takes.

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, efficient sentence with no redundant words. The em-dash structure front-loads the action and concisely lists the specific metrics, maximizing information density.

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 tool's simplicity (one parameter with complete schema coverage) and lack of output schema, the description adequately covers intent but leaves gaps regarding the return format and behavioral edge cases. It meets minimum viability but does not provide the richness expected when no annotations or output schema exist.

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%, establishing a baseline of 3. The description mentions 'multiple assets' which aligns with the 'symbols' parameter, but adds no additional semantic context (e.g., validation rules, format requirements, or examples) beyond what the schema already provides.

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 provides a clear verb ('Compare') and resource ('assets') and specifies the metrics involved ('prices, changes, market caps'). The 'side by side' phrasing implicitly distinguishes this from single-asset siblings like 'price' and 'order_book', though it does not explicitly contrast with 'analyze' or 'market_cap'.

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?

There is no guidance on when to use this tool versus siblings like 'analyze' (which might also examine multiple assets) or 'market_cap'. No prerequisites, filtering constraints, or alternative selection criteria are provided.

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