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; }

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