Skip to main content
Glama
CoinStatsHQ

CoinStats MCP Server

Official

get-market-cap

Retrieve global cryptocurrency market capitalization data to analyze total market value and track overall market trends.

Instructions

Get global market data.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Tool configuration object defining the schema (parameters), endpoint '/markets', method 'GET', and metadata for the 'get-market-cap' tool.
    {
        name: 'get-market-cap',
        description: 'Get global market data.',
        endpoint: '/markets',
        method: 'GET',
        parameters: {},
    },
  • The MCP tool handler function (async callback) registered for 'get-market-cap'. Since not local, calls universalApiHandler with endpoint '/markets', 'GET', and parameters.
    server.tool(config.name, config.description, config.parameters, async (params: Record<string, any>) => {
        // Handle local operations
        if (config.isLocal) {
            // Handle specific local tools
            if (config.name === 'save-share-token') {
                await saveToCache('shareToken', params.shareToken);
                return {
                    content: [
                        {
                            type: 'text',
                            text: 'Share token saved successfully',
                        },
                    ],
                };
            }
    
            if (config.name === 'get-share-token') {
                const shareToken = await getFromCache('shareToken');
    
                return {
                    content: [
                        {
                            type: 'text',
                            text: shareToken ? shareToken : 'No share token found in cache',
                            isError: !shareToken,
                        },
                    ],
                };
            }
            // Future local tools can be added here
    
            // Default response for unhandled local tools
            return {
                content: [
                    {
                        type: 'text',
                        text: 'Operation completed',
                    },
                ],
            };
        }
    
        // Handle API operations
        const basePath = config.basePath || COINSTATS_API_BASE;
        const method = config.method || 'GET';
    
        // Methods that typically have a request body
        const bodyMethods = ['POST', 'PUT', 'PATCH', 'DELETE'];
    
        // For GET/DELETE requests, all params go in the URL
        // For POST/PUT/PATCH, send params as the body
        if (bodyMethods.includes(method.toUpperCase())) {
            return universalApiHandler(basePath, config.endpoint, method, {}, params);
        } else {
            return universalApiHandler(basePath, config.endpoint, method, params);
        }
    });
  • Core implementation of the API request logic: processes endpoint and params, fetches from CoinStats API, handles path params and special cases, returns JSON response in MCP format.
    export async function universalApiHandler<T>(
        basePath: string,
        endpoint: string,
        method: string = 'GET',
        params: Record<string, any> = {},
        body?: any
    ): Promise<{
        content: Array<{ type: 'text'; text: string; isError?: boolean }>;
    }> {
        try {
            // Handle path parameters - replace {paramName} in endpoint with actual values
            let processedEndpoint = endpoint;
            let processedParams = { ...params };
    
            // Find all path parameters in the endpoint (e.g., {coinId}, {id}, {type})
            const pathParamMatches = endpoint.match(/\{([^}]+)\}/g);
    
            if (pathParamMatches) {
                for (const match of pathParamMatches) {
                    const paramName = match.slice(1, -1); // Remove { and }
    
                    if (processedParams[paramName] !== undefined) {
                        // Replace the placeholder with the actual value
                        processedEndpoint = processedEndpoint.replace(match, processedParams[paramName]);
                        // Remove the parameter from query params since it's now part of the path
                        delete processedParams[paramName];
                    } else {
                        throw new Error(`Required path parameter '${paramName}' is missing`);
                    }
                }
            }
    
            // MCP clients might not support '~' in parameter names, so we replace '-' with '~' specifically for the /coins endpoint before making the request.
            if (endpoint === '/coins') {
                processedParams = Object.entries(processedParams).reduce((acc, [key, value]) => {
                    acc[key.replace(/-/g, '~')] = value;
                    return acc;
                }, {} as Record<string, any>);
            }
    
            const url = `${basePath}${processedEndpoint}`;
            const data = await makeRequestCsApi<T>(url, method, processedParams, body);
    
            if (!data) {
                return {
                    content: [{ type: 'text', text: 'Something went wrong', isError: true }],
                };
            }
    
            return {
                content: [
                    {
                        type: 'text',
                        text: JSON.stringify(data),
                    },
                ],
            };
        } catch (error) {
            return {
                content: [{ type: 'text', text: `Error: ${error}`, isError: true }],
            };
        }
    }
  • src/index.ts:17-18 (registration)
    Registers all tools, including 'get-market-cap', by calling registerTools with the MCP server and tool configurations.
    // Register all tools from configurations
    registerTools(server, allToolConfigs);
  • Low-level HTTP request maker used by universalApiHandler to perform the actual fetch to the CoinStats API.
    export async function makeRequestCsApi<T>(url: string, method: string = 'GET', params: Record<string, any> = {}, body?: any): Promise<T | null> {
        const headers = {
            'X-API-KEY': COINSTATS_API_KEY,
            'Content-Type': 'application/json',
        };
    
        try {
            // Build request options
            const options: RequestInit = { method, headers };
    
            // Add body for non-GET requests if provided
            if (method !== 'GET' && body) {
                options.body = JSON.stringify(body);
            }
    
            // Add query params for all requests
            const queryParams = new URLSearchParams(params);
            const queryString = queryParams.toString();
            const urlWithParams = queryString ? `${url}?${queryString}` : url;
    
            const response = await fetch(urlWithParams, options);
            if (!response.ok) {
                throw new Error(`HTTP error! status: ${response.status}`);
            }
            return (await response.json()) as T;
        } catch (error) {
            return null;
        }
    }
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. 'Get global market data' provides no information about what the tool actually returns (format, structure, units), whether it requires authentication, rate limits, data freshness, or any behavioral characteristics. For a tool with zero annotation coverage, this description fails to provide any meaningful behavioral context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

While technically concise with only 4 words, this is under-specification rather than effective conciseness. The description fails to communicate essential information about what the tool does, making its brevity a liability. Every word should earn its place, but here the words don't provide enough value to justify their inclusion.

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

Completeness1/5

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

Given the complexity of financial market data tools and the complete lack of annotations and output schema, the description is woefully incomplete. It doesn't explain what 'market data' means, what format it returns, whether it's real-time or historical, what scope 'global' encompasses, or how this differs from numerous sibling tools. For a tool in a crowded namespace with no structured metadata, this description provides inadequate context.

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 tool has 0 parameters with 100% schema description coverage (empty schema). The description doesn't need to compensate for any parameter documentation gaps. While the description doesn't mention the lack of parameters, this isn't required when the schema fully documents the empty parameter set. The baseline for 0 parameters with high schema coverage is 4.

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

Purpose2/5

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

The description 'Get global market data' is vague and tautological - it essentially restates the tool name 'get-market-cap' without specifying what 'market data' means or what resource is being retrieved. It doesn't distinguish this tool from sibling tools like 'get-coins', 'get-exchanges', or 'get-currencies' which also retrieve market-related data. The purpose is unclear beyond a generic data retrieval statement.

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

Usage Guidelines1/5

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

The description provides absolutely no guidance on when to use this tool versus alternatives. With multiple sibling tools that retrieve market data (get-coins, get-exchanges, get-currencies, get-ticker-markets, etc.), there's no indication whether this tool provides market capitalization specifically, aggregated data, or some other subset. The agent has no way to determine when this tool is appropriate versus other market data tools.

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/CoinStatsHQ/coinstats-mcp'

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