Skip to main content
Glama

get_market_and_price_endpoints

Access real-time and historical cryptocurrency market data, prices, trading volumes, and analytics including CEX trading, derivatives pricing, and social sentiment metrics.

Instructions

Get all endpoints in the "Market Data and Price" category. Endpoints to retrieve real-time and historical cryptocurrency prices, market caps, trading volumes, OHLC data, global market statistics, supported currencies, basic market performance metrics across different timeframes and asset platforms, stablecoin market analytics, stablecoin price tracking, comprehensive stablecoin market cap data across multiple chains, social sentiment-enhanced market metrics including Galaxy Score™ and AltRank™ rankings, centralized exchange (CEX) trading data including real-time tickers, order books, recent trades, candlestick charts, best bid/ask prices, derivatives pricing (index, mark, and premium), and perpetual futures funding rates across major exchanges.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Registry entry that defines the 'get_market_and_price_endpoints' tool name, category, description, and list of sub-tools it aggregates.
    {
      "category": "Market Data and Price",
      "name": "get_market_and_price_endpoints",
      "description": "Endpoints to retrieve real-time and historical cryptocurrency prices, market caps, trading volumes, OHLC data, global market statistics, supported currencies, basic market performance metrics across different timeframes and asset platforms, stablecoin market analytics, stablecoin price tracking, comprehensive stablecoin market cap data across multiple chains, social sentiment-enhanced market metrics including Galaxy Score™ and AltRank™ rankings, centralized exchange (CEX) trading data including real-time tickers, order books, recent trades, candlestick charts, best bid/ask prices, derivatives pricing (index, mark, and premium), and perpetual futures funding rates across major exchanges.",
      "tools": [
        "coins_index",
        "coins_market_data_browser", 
        "coins_history_browser",
        "range_coins_market_chart_browser",
        "range_coins_ohlc_browser",
        "simple_price_browser",
        "gainers_losers_browser",
        "contract_coins_browser",
        "range_contract_coins_market_chart_browser",
        "id_simple_token_price_browser",
        "global_browser",
        "simple_supported_vs_currencies_browser",
        // "get_token_prices_browser",  defi
        // "get_historical_prices_browser", defi
        "retrieve_token_pricing",
        "fetch_price_chart_data",
        "fetch_token_mini_charts",
        "fetch_token_chart_urls",
        "coin_tickers_data",
        "coin_historical_chart", 
        "btc_exchange_rates",
        "global_market_cap_chart",
        "companies_crypto_treasury",
        "stablecoins_list",
        "stablecoin_chains_list",
        "stablecoin_charts_global",
        "stablecoin_charts_by_chain",
        "stablecoin_prices_current",
        "scan_crypto_market_metrics",
        "analyze_coin_performance",
        "browse_supported_stocks",
        "retrieve_stock_analytics",
        "trading_pair_ticker_data",
        "multiple_tickers_data",
        "trading_pair_orderbook_data",
        "trading_pair_recent_trades",
        "trading_pair_candlestick_data",
        "multiple_pairs_best_prices",
        "level2_orderbook_data",
        "derivatives_index_candlestick",
        "derivatives_mark_candlestick",
        "perpetual_premium_index_data",
        "perpetual_funding_rate_current",
        "perpetual_funding_rate_history",
        "perpetual_funding_rates_all"
      ]
    },
  • Code that dynamically creates the tool object for 'get_market_and_price_endpoints' (and other categories), including its empty input schema, description, and handler function that fetches and returns the list of tools in the category.
    // Create category-specific endpoints that act as list functionality
    const categoryTools = ToolRegistry.map(category => {
      const categorySchema = z.object({});
      
      const categoryEndpointName = category.name;
      
      return {
        metadata: {
          resource: 'dynamic_tools',
          operation: 'read' as const,
          tags: ['category'],
        },
        tool: {
          name: categoryEndpointName,
          description: `Get all endpoints in the "${category.category}" category. ${category.description}`,
          inputSchema: zodToInputSchema(categorySchema),
        },
        handler: async (
          args: Record<string, unknown> | undefined,
        ): Promise<any> => {
          const toolsInCategory = getAllToolsInCategory(category.category);
          
          return asTextContentResult({
            category: category.category,
            description: category.description,
            tools: toolsInCategory.map((tool ) => ({
              name: tool.name,
              description: tool.description
            })),
          });
        },
      };
    });
    
    return [getEndpointTool, callEndpointTool, ...categoryTools];
  • Helper function called by the handler to format the category tools list as MCP-compatible text content, with automatic truncation for large responses.
    export function asTextContentResult(result: Object): any {
      // return {data: result}
      // Estimate token count (roughly 4 chars per token)
      const MAX_TOKENS = 25000;
      const CHARS_PER_TOKEN = 4;
      const maxChar = MAX_TOKENS * CHARS_PER_TOKEN; // ~100,000 chars for 25k tokens
      
      const jsonString = JSON.stringify(result, null, 2);
      
      if (jsonString.length > maxChar) {
        // Try to intelligently truncate if it's an array
        if (Array.isArray(result)) {
          const truncatedArray = result.slice(0, Math.floor(result.length * maxChar / jsonString.length));
          const truncatedJson = JSON.stringify({
            results: truncatedArray,
            truncated: true,
            originalLength: result.length,
            returnedLength: truncatedArray.length,
            message: "Response truncated due to size limits. Consider using pagination."
          }, null, 2);
          
          return {
            content: [
              {
                type: 'text',
                text: truncatedJson,
              },
            ],
          };
        }
        
        // For objects with results array
        if (typeof result === 'object' && result !== null && 'results' in result && Array.isArray((result as any).results)) {
          const originalResults = (result as any).results;
          const estimatedItemSize = jsonString.length / originalResults.length;
          const maxItems = Math.floor(maxChar / estimatedItemSize);
          
          const truncatedResult = {
            ...result,
            results: originalResults.slice(0, maxItems),
            truncated: true,
            originalCount: originalResults.length,
            returnedCount: maxItems,
            message: "Response truncated due to size limits. Use pagination parameters (limit/offset) for more results."
          };
          
          return {
            content: [
              {
                type: 'text',
                text: JSON.stringify(truncatedResult, null, 2),
              },
            ],
          };
        }
        
        // Fallback to simple truncation
        const truncated = jsonString.substring(0, maxChar) + '\n... [TRUNCATED DUE TO SIZE LIMITS]';
        return {
          content: [
            {
              type: 'text',
              text: truncated,
            },
          ],
        };
      }
      
      return {
        content: [
          {
            type: 'text',
            text: jsonString,
          },
        ],
      };
    }
  • Helper function invoked by the handler to retrieve the full tool objects matching the names listed in the category registry.
    export function getAllToolsInCategory(category: string){
      let categoryUsed = ToolRegistry.find(tool => tool.category === category);
      if(!categoryUsed){
        return []
      }
      const allWrappedTools = supportedTools
      // return all the tools from wrapped tools that are in the category (name match)
      let toolsInCategory = [];
      for (const tool of categoryUsed.tools){
        const wrappedTool = allWrappedTools.find(wrappedTool => wrappedTool.name === tool);
        if(wrappedTool){
          toolsInCategory.push(wrappedTool);
        }
        else console.log(`Tool ${tool} not found in wrapped tools`);
      }
      return toolsInCategory;
    }
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 describes what data is retrieved but lacks details on how the tool behaves: e.g., whether it returns a list, pagination, rate limits, authentication needs, or error handling. The description is informative about content but misses operational traits, which is a significant gap for a tool with zero annotation coverage.

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?

The description is a single run-on sentence that lists numerous data types in a dense, unstructured manner. While it front-loads the core purpose ('Get all endpoints...'), the extensive enumeration of examples (e.g., 'stablecoin market analytics', 'perpetual futures funding rates') adds verbosity without clear organization, making it less efficient and harder 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 complexity implied by the broad data scope and lack of annotations or output schema, the description is incomplete. It details what data is included but omits critical behavioral aspects (e.g., return format, pagination, errors) and doesn't address how to use the retrieved endpoints. For a tool with no structured support fields, this leaves significant gaps in understanding its practical use.

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 0 parameters with 100% coverage, so no parameter documentation is needed. The description appropriately adds no parameter details, as there are none to explain. This meets the baseline for a parameterless tool, though it doesn't compensate for any gaps since none exist.

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 tool's purpose: 'Get all endpoints in the "Market Data and Price" category.' It specifies the resource (endpoints) and category scope, though it doesn't explicitly differentiate from siblings like 'get_api_endpoint_schema' or 'get_search_discovery_endpoints' beyond the category name. The detailed list of included data types (e.g., cryptocurrency prices, market caps) adds specificity but doesn't directly contrast with other tools.

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. It lists what the tool retrieves but doesn't mention when to choose it over siblings like 'get_api_endpoint_schema' (for schema details) or 'get_search_discovery_endpoints' (for search-related endpoints). There's no explicit context, exclusions, or prerequisites stated, leaving usage decisions unclear.

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/hive-intel/hive-crypto-mcp'

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