Skip to main content
Glama

get_token_contract_endpoints

Retrieve comprehensive token and contract data endpoints for detailed analysis, including metadata, holder distributions, contract details, transaction forensics, and address tracking across multiple networks. Ideal for security analysis, token discovery, and lifecycle event monitoring.

Instructions

Get all endpoints in the "Token & Contract data" category. Endpoints for detailed token and contract analysis including token metadata, holder distributions, contract information, token filtering and discovery, holder rankings, comprehensive token intelligence across multiple networks, advanced transaction analysis and forensics, detailed transaction data (hash, sender, recipient, value, gas costs), internal transactions with signatures, transaction status validation, address tracking capabilities for security analysis and investigation, token lifecycle events, trader analytics, and project metadata including websites and social media links.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Shared handler for all category endpoint tools (including get_token_contract_endpoints). Retrieves tools from the specific category using getAllToolsInCategory, maps to name/description, and returns formatted text content.
    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 object creation within the dynamic map over ToolRegistry, setting tool.name to category.name ("get_token_contract_endpoints"), description, metadata, and inputSchema.
    const categoryEndpointName = category.name;
  • Empty Zod schema (z.object({})) used for input validation of category endpoint tools like get_token_contract_endpoints (no parameters required).
    const categorySchema = z.object({});
  • ToolRegistry category definition providing the name, description, and list of sub-tool names used to create and populate the get_token_contract_endpoints tool.
    {
      "category": "Token & Contract data",
      "name": "get_token_contract_endpoints",
      "description": "Endpoints for detailed token and contract analysis including token metadata, holder distributions, contract information, token filtering and discovery, holder rankings, comprehensive token intelligence across multiple networks, advanced transaction analysis and forensics, detailed transaction data (hash, sender, recipient, value, gas costs), internal transactions with signatures, transaction status validation, address tracking capabilities for security analysis and investigation, token lifecycle events, trader analytics, and project metadata including websites and social media links.",
      "tools": [
        "address_networks_onchain_tokens_browser",
        "tokens_networks_onchain_info_browser",
        "tokens_networks_onchain_top_holders_browser", 
        "tokens_networks_onchain_holders_chart_browser",
        "retrieve_token_details",
        "fetch_multiple_tokens",
        "search_tokens_by_criteria",
        "list_token_holders",
        "calculate_top_holders_percentage",
        "list_newest_token_contracts",
        "multi_tokens_data",
        "tokens_recent_updates",
        "token_lifecycle_events",
        "token_top_traders_stats",
        "fetch_coin_metadata"
      ]
  • Helper function invoked by the tool handler to match category tool names against supportedTools and return the full tool objects for the category.
    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 the endpoints cover (e.g., token metadata, transaction analysis) but doesn't mention operational traits like rate limits, authentication needs, pagination, or error handling. For a tool with zero annotation coverage, this leaves significant gaps in understanding how to interact with it effectively.

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 starts with a clear purpose but then devolves into a long, comma-separated list of endpoint capabilities (e.g., 'token metadata, holder distributions...'). This information could be condensed or omitted, as it doesn't directly help the agent invoke the tool. The lack of front-loading and excessive detail reduces clarity.

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 endpoint list and lack of annotations or output schema, the description is incomplete. It doesn't explain what the tool returns (e.g., a list of endpoint names, full configurations) or how to handle the data. For a tool with no structured output information, more guidance on expected behavior is needed.

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, which aligns with the schema. A baseline of 4 is applied since the description doesn't need to compensate for any parameter 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 "Token & Contract data" category.' It specifies the verb ('Get') and resource ('endpoints'), and the category name distinguishes it from sibling tools like 'get_defi_protocol_endpoints' or 'get_nft_analytics_endpoints'. However, it doesn't explicitly differentiate beyond the category name, which is why it's a 4 rather than a 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 alternatives. It lists what the endpoints cover but doesn't mention prerequisites, exclusions, or compare it to sibling tools like 'get_api_endpoint_schema' or 'call_api_endpoint'. Without this context, the agent must infer usage from the category name alone.

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