Skip to main content
Glama
truss44

Crypto Price & Market Analysis MCP Server

get-market-analysis

Analyze cryptocurrency market data by retrieving detailed insights on top exchanges and volume distribution. Input a cryptocurrency symbol (e.g., BTC, ETH) to access comprehensive market trends and exchange information.

Instructions

Get detailed market analysis including top exchanges and volume distribution

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolYesCryptocurrency symbol (e.g., BTC, ETH)

Implementation Reference

  • src/index.ts:51-63 (registration)
    Registers the 'get-market-analysis' tool with the MCP server, specifying title, description, input schema, and handler function that calls handleGetMarketAnalysis.
    server.registerTool(
      "get-market-analysis",
      {
        title: "Get Market Analysis",
        description:
          "Get detailed market analysis including top exchanges and volume distribution",
        inputSchema: GetMarketAnalysisSchema.shape,
      },
      async (args, _extra) => {
        const result = await handleGetMarketAnalysis(args);
        return result as any;
      }
    );
  • Zod schema for input validation of the get-market-analysis tool, requiring a 'symbol' string.
    export const GetMarketAnalysisSchema = z.object({
      symbol: z.string().min(1),
    });
  • Main handler function for get-market-analysis tool. Parses input symbol, fetches asset data from CoinCap, finds the asset, gets its markets, formats analysis, and returns markdown content or error.
    export async function handleGetMarketAnalysis(args: unknown) {
      const { symbol } = GetMarketAnalysisSchema.parse(args);
      const upperSymbol = symbol.toUpperCase();
    
      try {
        const assetsData = await getAssets();
        
        if (!assetsData) {
          return {
            content: [{ type: "text", text: "Failed to retrieve cryptocurrency data" }],
          };
        }
        
        const asset = assetsData.data.find(
          (a: { symbol: string; }) => a.symbol.toUpperCase() === upperSymbol
        );
    
        if (!asset) {
          return {
            content: [{ type: "text", text: `Could not find cryptocurrency with symbol ${upperSymbol}` }],
          };
        }
    
        const marketsData = await getMarkets(asset.id);
        
        if (!marketsData) {
          return {
            content: [{ type: "text", text: "Failed to retrieve market data" }],
          };
        }
        
        return {
          content: [{ type: "text", text: formatMarketAnalysis(asset, marketsData.data) }],
        };
      } catch (error) {
        return {
          content: [{ 
            type: "text", 
            text: error instanceof Error ? error.message : `Failed to retrieve data: ${String(error)}` 
          }],
        };
      }
    }
Behavior2/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 states the tool retrieves analysis but doesn't mention whether it's a read-only operation, requires authentication, has rate limits, or what the output format looks like. For a tool with no annotations, this leaves significant gaps in understanding its behavior.

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

Conciseness4/5

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

The description is a single, efficient sentence that front-loads the purpose without unnecessary details. It avoids redundancy and waste, though it could be slightly more structured by explicitly separating key components like scope or limitations.

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 complexity of market analysis, no annotations, and no output schema, the description is incomplete. It doesn't explain what 'detailed market analysis' entails beyond top exchanges and volume distribution, nor does it cover behavioral aspects like data freshness or error handling, leaving the agent with insufficient context.

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?

The input schema has 100% description coverage, with the 'symbol' parameter clearly documented. The description adds no additional parameter details beyond what the schema provides, such as examples of analysis outputs or constraints. With high schema coverage, the baseline score of 3 is appropriate as the schema does the heavy lifting.

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 clearly states the verb 'Get' and the resource 'detailed market analysis', specifying it includes 'top exchanges and volume distribution'. This distinguishes it from sibling tools like 'get-crypto-price' (price only) and 'get-historical-analysis' (historical trends), though it doesn't explicitly mention how it differs from them.

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?

No guidance is provided on when to use this tool versus alternatives like 'get-crypto-price' or 'get-historical-analysis'. The description implies usage for market analysis details but doesn't specify scenarios, prerequisites, or exclusions, leaving the agent to infer context.

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

Related 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/truss44/mcp-crypto-price'

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