Skip to main content
Glama

get_search_discovery_endpoints

Retrieve all endpoints in the Search & Discovery category for cryptocurrency search, trending analysis, token discovery, new coin listings, and market-wide search capabilities.

Instructions

Get all endpoints in the "Search & Discovery" category. Endpoints for cryptocurrency search functionality, trending analysis, coin categorization, token discovery, new coin listings, comprehensive search capabilities across coins, categories, and markets, event categorization and labeling systems.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Dynamically generates the MCP tool 'get_search_discovery_endpoints' (when processing ToolRegistry entry for Search & Discovery category). Defines empty input schema, tool metadata, and handler that lists available tools in the category by fetching via getAllToolsInCategory, mapping to name/description, and formatting as text content.
    // 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];
  • Registry entry defining 'get_search_discovery_endpoints' as the discovery tool name for the Search & Discovery category, listing the specific tools it exposes.
    {
      "category": "Search & Discovery",
      "name": "get_search_discovery_endpoints",
      "description": "Endpoints for cryptocurrency search functionality, trending analysis, coin categorization, token discovery, new coin listings, comprehensive search capabilities across coins, categories, and markets, event categorization and labeling systems.",
      "tools": [
        "search_browser",
        "search_trending_browser",
        "coins_categories_browser",
        "coins_list_browser", 
        "new_coins_list_browser",
        "coins_categories_market_data",
        "exchanges_list_simple", 
        "derivatives_exchanges_list",
        "event_labels_list"
      ]
    },
  • Helper function called by the tool handler to retrieve the full tool definitions for the category by matching names from registry against supportedTools.
    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;
    }
  • Maps category index 8 (Search & Discovery) to HTTP MCP endpoint '/hive_search_discovery/mcp' (though HTTP server code is currently commented out).
    8: "/hive_search_discovery/mcp",      // Search & Discovery
    9: "/hive_social_sentiment/mcp"       // Social Media & Sentiment Analytics
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 'Get all endpoints' but does not clarify if this is a read-only operation, if it requires authentication, what the return format is (e.g., list, JSON), or any rate limits. The description lists examples of endpoint types but lacks operational details, making it insufficient 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.

Conciseness3/5

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

The description is front-loaded with the core purpose but becomes verbose with a long list of examples (e.g., 'cryptocurrency search functionality, trending analysis...'). While these examples add context, they could be more streamlined. The structure is adequate but not optimally concise, as some sentences could be condensed without losing meaning.

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

Completeness3/5

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

Given the tool's complexity (simple retrieval with no parameters) and lack of annotations and output schema, the description is moderately complete. It explains what the tool returns (endpoints in a specific category with examples) but misses key behavioral aspects like response format or operational constraints. For a zero-parameter tool, it provides enough context to understand the scope but not full operational guidance.

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, and the input schema has 100% description coverage (though empty). The description does not need to add parameter details, so it appropriately focuses on the tool's purpose. Since there are no parameters, a baseline score of 4 is applied, as the description compensates by explaining what the tool does without unnecessary parameter information.

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 "Search & Discovery" category.' It specifies the verb ('Get') and resource ('endpoints'), and the following list provides concrete examples of what these endpoints cover (e.g., cryptocurrency search, trending analysis). However, it does not explicitly differentiate from sibling tools like 'get_api_endpoint_schema' or 'call_api_endpoint', which slightly limits its clarity in context.

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 does not mention sibling tools or contexts where this tool is preferred, such as for retrieving endpoints related to search and discovery versus other categories like 'get_market_and_price_endpoints'. This lack of comparative guidance leaves the agent without explicit usage instructions.

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