Skip to main content
Glama
TaylorChen

Multi-MCPs

by TaylorChen

get_market_data

Retrieve cryptocurrency market data for a specified coin, providing price and trading information through the Multi-MCPs server's unified API integration.

Instructions

Get market data for a coin

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
coin_idYes

Implementation Reference

  • The handler function that executes the get_market_data tool: extracts coin_id from input arguments, validates it, and delegates to the CoinGeckoClient's getMarketData method.
    async get_market_data(args: Record<string, unknown>) {
      const coinId = String(args.coin_id || "");
      if (!coinId) throw new Error("coin_id is required");
      return client.getMarketData(coinId);
    },
  • Input schema for the get_market_data tool, requiring a 'coin_id' string parameter.
    inputSchema: {
      type: "object",
      properties: { coin_id: { type: "string" } },
      required: ["coin_id"],
    },
  • Tool registration object for get_market_data, including name, description, and input schema, added to the tools array in registerCoinGecko().
    {
      name: "get_market_data",
      description: "Get market data for a coin",
      inputSchema: {
        type: "object",
        properties: { coin_id: { type: "string" } },
        required: ["coin_id"],
      },
    },
  • Helper method in CoinGeckoClient class that fetches market data from CoinGecko API for a given coin ID.
    getMarketData(coinId: string) {
      return this.request(`/coins/${coinId}`);
    }
Behavior1/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It fails to mention any behavioral traits such as read-only vs. mutative nature, authentication needs, rate limits, error handling, or response format. The description is too vague to inform the agent about how the tool behaves beyond its basic function.

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 extremely concise with a single sentence, 'Get market data for a coin', which is front-loaded and wastes no words. It efficiently communicates the core purpose without unnecessary elaboration, making it easy to parse quickly.

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 the tool's complexity (a data retrieval tool with no output schema and low schema coverage), the description is incomplete. It does not explain what 'market data' includes (e.g., price, volume, trends), how results are returned, or any limitations. With no annotations and minimal parameter info, the description fails to provide sufficient context for effective tool use.

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

Parameters2/5

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

The input schema has 0% description coverage, with one parameter 'coin_id' undocumented. The description does not add any meaning beyond the schema, such as explaining what 'coin_id' represents (e.g., cryptocurrency symbol, name, or ID format) or providing examples. It fails to compensate for the low schema coverage, leaving the parameter semantics unclear.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the tool's purpose as 'Get market data for a coin', which includes a verb ('Get') and resource ('market data for a coin'), making it clear what it does. However, it does not distinguish from sibling tools like 'get_coin_price' or 'get_trending_coins', leaving ambiguity about scope or differences.

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 such as 'get_coin_price' or 'get_trending_coins'. It lacks context about prerequisites, exclusions, or specific use cases, offering only a basic statement of purpose without operational direction.

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/TaylorChen/muti-mcps'

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