Skip to main content
Glama

get_network_infrastructure_endpoints

Retrieve endpoints for blockchain network and infrastructure data, including network health, gas prices, mempool monitoring, transaction analysis, and exchange infrastructure status across major platforms.

Instructions

Get all endpoints in the "Network & Infrastructure" category. Endpoints for blockchain network information, network health monitoring, gas price tracking, network statistics, asset platform data, infrastructure metrics across different blockchain networks, real-time mempool monitoring, pending transaction analysis, transaction status simulation, MEV detection and protection, gas fee optimization, arbitrage opportunity identification, comprehensive blockchain activity monitoring, community-contributed insights and annotations, data platform system updates monitoring, centralized exchange (CEX) infrastructure including system status monitoring, server time synchronization, available trading markets/pairs browsing, and supported currencies listing across major exchanges.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler implementation for the 'get_network_infrastructure_endpoints' tool. This shared handler for category endpoint tools calls getAllToolsInCategory to retrieve the list of tools in the 'Network & Infrastructure' category and formats them into a response listing tool names and descriptions.
    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
        })),
      });
    },
  • Tool registry entry defining the name, description, and list of underlying tools for 'get_network_infrastructure_endpoints'.
    {
      "category": "Network & Infrastructure",
      "name": "get_network_infrastructure_endpoints",
      "description": "Endpoints for blockchain network information, network health monitoring, gas price tracking, network statistics, asset platform data, infrastructure metrics across different blockchain networks, real-time mempool monitoring, pending transaction analysis, transaction status simulation, MEV detection and protection, gas fee optimization, arbitrage opportunity identification, comprehensive blockchain activity monitoring, community-contributed insights and annotations, data platform system updates monitoring, centralized exchange (CEX) infrastructure including system status monitoring, server time synchronization, available trading markets/pairs browsing, and supported currencies listing across major exchanges.",
      "tools": [
        "onchain_networks_browser",
        "list_blockchain_networks",
        "check_network_health",
        "fetch_network_metrics",
        "get_gas_prices", 
        "asset_platforms_browser",
        "community_notes_data",
        "monitor_system_updates",
        "exchange_system_status",
        "exchange_server_time",
        "exchange_markets_browser",
        "exchange_currencies_browser"
      ]
  • Tool schema definition (empty input schema since no parameters required) for category endpoint tools including 'get_network_infrastructure_endpoints'.
    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),
  • Helper function getAllToolsInCategory used by the tool handler to resolve tool names in the category to full tool objects from 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;
    }
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description must fully disclose behavioral traits. It states the tool retrieves endpoints but doesn't describe how (e.g., format, pagination, rate limits, authentication needs, or error handling). The list of endpoint types implies breadth but lacks operational details, leaving significant gaps in understanding the tool's behavior.

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 overly verbose and poorly structured. It's a single run-on sentence listing numerous endpoint types without prioritization or grouping, making it hard to parse. While it covers many details, the lack of organization and excessive length reduces clarity and efficiency.

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 extensive list of endpoint types and the absence of annotations and output schema, the description is incomplete. It doesn't explain what the tool returns (e.g., a list, format, or structure), how to handle the data, or any limitations. For a tool with no structured support, this leaves too many operational questions unanswered.

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 doesn't discuss parameters, focusing instead on the tool's scope. Since there are no parameters, the baseline is 4, as the description doesn't need to compensate for any schema gaps.

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 "Network & Infrastructure" category.' It specifies the verb ('Get') and resource ('endpoints'), and provides a comprehensive list of what those endpoints cover, making the purpose unambiguous. However, it doesn't explicitly distinguish this tool from its siblings (e.g., 'get_defi_protocol_endpoints'), which prevents a score of 5.

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 its siblings. It lists many types of endpoints covered but doesn't explain how this differs from tools like 'get_onchain_dex_pool_endpoints' or 'get_market_and_price_endpoints'. There's no mention of prerequisites, alternatives, or exclusions, leaving usage context 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