Skip to main content
Glama

get_nft_analytics_endpoints

Access all NFT analytics endpoints to analyze NFT ecosystems, including collection data, market trends, trading volumes, liquidity pools, and cross-chain insights.

Instructions

Get all endpoints in the "NFT Analytics" category. Endpoints for comprehensive NFT ecosystem analysis including collection data, market analytics, user NFT holdings, collection floor prices, trading volumes, historical NFT market data, NFT liquidity pools and AMM marketplaces (like Sudoswap), NFT DeFi analytics, Prime ecosystem pools, Parallel trading card game assets, NFT pool management, collection holder analysis, advanced NFT search and filtering, contract metadata, cross-chain NFT analytics, social sentiment tracking for NFT collections, and time series market trend analysis.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The core handler function for the 'get_nft_analytics_endpoints' tool. It calls getAllToolsInCategory('NFT Analytics') to retrieve the list of tools in this category from supportedTools, formats the response with category info and tool names/descriptions, and uses asTextContentResult to handle output formatting and truncation.
        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
          })),
        });
      },
    };
  • Dynamic registration of category endpoint tools, including 'get_nft_analytics_endpoints'. Maps over ToolRegistry to create a tool for each category with name from category.name, empty input schema, and the shared handler logic.
    // 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];
  • Input schema for category endpoint tools (empty object since no parameters are required). Converted to JSON schema via zodToInputSchema.
    const categorySchema = z.object({});
  • Source metadata for the NFT Analytics category used to dynamically create the 'get_nft_analytics_endpoints' tool name, description, and list of underlying tool names to match against supportedTools.
    {
      "category": "NFT Analytics",
      "name": "get_nft_analytics_endpoints",
      "description": "Endpoints for comprehensive NFT ecosystem analysis including collection data, market analytics, user NFT holdings, collection floor prices, trading volumes, historical NFT market data, NFT liquidity pools and AMM marketplaces (like Sudoswap), NFT DeFi analytics, Prime ecosystem pools, Parallel trading card game assets, NFT pool management, collection holder analysis, advanced NFT search and filtering, contract metadata, cross-chain NFT analytics, social sentiment tracking for NFT collections, and time series market trend analysis.",
      "tools": [
        "id_nfts_browser",
        "list_nfts_browser",
        "nfts_market_chart_browser",
        "get_nft_list", 
        "get_all_nft",
        "get_nft_collection",
        "nft_pool_details",
        "nft_pool_events_data",
        "nft_collection_pool_stats",
        "exchange_nft_collections",
        "collection_exchange_pools",
        "owner_nft_pools",
        "nft_collections_search",
        "nft_pool_collections_search",
        "nfts_search_advanced",
        "nft_pools_search",
        "nft_collection_assets",
        "nft_collection_detailed_stats",
        "nft_collection_events",
        "nft_contracts_metadata",
        "parallel_assets_search",
        "parallel_card_changes",
        "prime_pool_assets_data",
        "prime_pool_events_data",
        "prime_pools_info",
        "nft_collection_holders",
        "prime_token_holders",
        "explore_nft_collections",
        "analyze_nft_collection",
        "track_nft_market_trends"
      ]
    },
  • Helper function called by the handler to resolve the list of actual tool objects from supportedTools by matching names in the NFT category's 'tools' array.
    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. It describes what the endpoints cover but lacks behavioral details: it doesn't specify if this is a read-only operation, potential rate limits, authentication needs, response format, or pagination. The description is informative about scope but misses key operational traits.

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 overly verbose with a long list of features. Sentences like 'Endpoints for comprehensive NFT ecosystem analysis...' could be more concise. While informative, the list of examples (e.g., 'collection floor prices, trading volumes') adds bulk without critical guidance, reducing efficiency.

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 simplicity (0 parameters, no output schema, no annotations), the description is moderately complete. It explains the category and examples well but lacks behavioral context and usage guidelines. For a no-param tool, this is adequate but has clear gaps in transparency and sibling differentiation.

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 schema description coverage is 100%. The description doesn't need to explain parameters, and it appropriately focuses on the tool's function. A baseline of 4 is applied since no parameters exist, and the description adds value by detailing the category scope without redundancy.

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 "NFT Analytics" category.' It specifies the verb ('Get') and resource ('endpoints'), and distinguishes the category ('NFT Analytics'). However, it doesn't explicitly differentiate from sibling tools like 'get_search_discovery_endpoints' or 'get_social_sentiment_endpoints' that might overlap, preventing a perfect score.

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 many features covered by the endpoints but doesn't mention sibling tools or contexts where other tools might be more appropriate. For example, it doesn't clarify if this should be used instead of 'get_social_sentiment_endpoints' for NFT-related sentiment.

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