Skip to main content
Glama
VENTURE-AI-LABS

CryptoDataAPI MCP Server

get_coin_profile

Retrieve comprehensive cryptocurrency data including price, market cap, historical changes, supply metrics, and descriptive details for informed analysis.

Instructions

Get a detailed profile for a specific cryptocurrency by symbol (e.g., BTC, ETH, SOL). Returns current price, market cap, 24h/7d/30d price changes, volume, circulating supply, ATH/ATL data, category tags, and description. Use search_coins first if you're unsure of the exact symbol.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolYesCoin symbol in uppercase (e.g., BTC, ETH, SOL, DOGE)

Implementation Reference

  • The handler function that executes the logic for the "get_coin_profile" tool. It fetches coin data from the API using the provided symbol.
    export async function handler(args: z.infer<typeof schema>) {
      return apiGet(`/api/v1/coins/${args.symbol.toUpperCase()}`);
    }
  • The Zod schema defining the expected input for the "get_coin_profile" tool.
    export const schema = z.object({
      symbol: z
        .string()
        .describe("Coin symbol in uppercase (e.g., BTC, ETH, SOL, DOGE)"),
    });
  • src/index.ts:55-78 (registration)
    The tool registration loop in src/index.ts that registers all tools, including "get_coin_profile", into the McpServer.
    for (const tool of tools) {
      server.tool(tool.name, tool.description, tool.schema.shape, async (args: Record<string, unknown>) => {
        const result = await tool.handler(args as any);
        if (result.ok) {
          return {
            content: [
              {
                type: "text" as const,
                text: JSON.stringify(result.data, null, 2),
              },
            ],
          };
        } else {
          return {
            content: [
              {
                type: "text" as const,
                text: `API Error (${result.status}): ${result.error}`,
              },
            ],
            isError: true,
          };
        }
      });
Behavior3/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 describes the tool as a read operation ('Get') and details the returned data, which covers basic behavior. However, it lacks information on potential errors (e.g., invalid symbols), rate limits, authentication needs, or data freshness, leaving gaps in transparency for a tool with no annotations.

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 front-loaded with the core purpose, followed by details on returned data and usage guidance. Both sentences are essential: the first defines the tool's function and output, and the second provides critical context for tool selection. There is no wasted text, making it highly efficient and well-structured.

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

Completeness4/5

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

Given the tool's complexity (single parameter, no output schema, no annotations), the description is largely complete. It covers purpose, output details, and usage guidelines effectively. However, it lacks explicit information on error handling or data sources, which could be useful for an agent. With no output schema, the description's detail on return values is beneficial but not exhaustive.

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 100% description coverage, so the schema already documents the single parameter 'symbol' with its type and format. The description adds value by providing context: it explains the parameter's role ('by symbol'), gives examples (BTC, ETH, SOL), and clarifies that symbols should be exact, which enhances understanding beyond the schema's technical specification.

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 tool's purpose with a specific verb ('Get') and resource ('detailed profile for a specific cryptocurrency by symbol'), and distinguishes it from sibling tools by mentioning 'search_coins' as an alternative for symbol uncertainty. It explicitly lists the returned data fields (price, market cap, changes, etc.), making the purpose highly specific and differentiated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit guidance on when to use this tool vs. alternatives: 'Use search_coins first if you're unsure of the exact symbol.' This directly addresses the sibling tool 'search_coins' and gives a clear conditional for tool selection, which is optimal for agent decision-making.

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/VENTURE-AI-LABS/cryptodataapi-mcp'

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