Skip to main content
Glama
tatumio

Tatum MCP Server

Official

gateway_get_supported_chains

Retrieve a list of all supported blockchain chains to identify network compatibility and integration options with Tatum MCP Server.

Instructions

[gateway] Get a list of all supported blockchain chains

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The core handler function that returns the list of supported blockchain chains. It ensures the service data is loaded and returns a copy of the cached chain names.
    public async getSupportedChains(): Promise<string[]> {
      await this.ensureDataLoaded();
      return [...this.cachedChains]; // Return a copy to prevent mutation
    }
  • The tool's schema definition, specifying name, description, and empty input schema (no parameters required).
      name: 'gateway_get_supported_chains',
      description: "Get a list of all supported blockchain networks available through Tatum's RPC gateways",
      inputSchema: {
        type: 'object',
        properties: {},
        required: []
      }
    },
    {
  • src/index.ts:78-80 (registration)
    Tool handler registration in the executeGatewayTool switch statement, dispatching to the GatewayService implementation.
    case 'gateway_get_supported_chains':
      return await this.gatewayService.getSupportedChains();
  • src/index.ts:193-196 (registration)
    Registration of all gateway tools (including this one) in the MCP server's listTools response handler.
    ...GATEWAY_TOOLS.map(tool => ({
      name: tool.name,
      description: `[gateway] ${tool.description}`,
      inputSchema: tool.inputSchema
  • Helper method that initializes the service by fetching blockchain data from Tatum API and populating the cachedChains used by the handler.
    public async initialize(): Promise<void> {
      if (this.dataFetched) {
        return;
      }
    
      try {
        console.error('Fetching blockchain data from Tatum API...');
        const response = await fetch(this.BLOCKCHAINS_URL);
        
        if (!response.ok) {
          throw new Error(`HTTP error! status: ${response.status}`);
        }
    
        const externalBlockchains: ExternalBlockchain[] = await response.json();
        
        // Transform external data to internal format
        this.cachedGateways = this.transformToGateways(externalBlockchains);
        this.cachedChains = this.extractChainNames(externalBlockchains);
        
        this.dataFetched = true;
        console.error(`Loaded ${this.cachedChains.length} networks from ${this.cachedGateways.length} blockchains`);
      } catch (error) {
        console.error('Failed to fetch blockchain data:', error instanceof Error ? error.message : 'Unknown error');
        
        // Fallback to empty data
        this.cachedGateways = [];
        this.cachedChains = [];
        this.dataFetched = true;
        
        throw new Error(`Failed to initialize GatewayService: ${error instanceof Error ? error.message : 'Unknown error'}`);
      }
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions it's a read operation ('Get a list'), but lacks details on response format, pagination, rate limits, or authentication needs. This is inadequate 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.

Conciseness5/5

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

The description is a single, efficient sentence with no wasted words. It's front-loaded with the core purpose, making it easy to parse quickly. Every word earns its place.

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 lack of annotations and output schema, the description is incomplete. It doesn't explain what the returned list includes (e.g., chain IDs, names, types), how it's structured, or any limitations. For a tool with no structured output documentation, this leaves significant gaps.

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 schema description coverage is 100% (though trivial since there are no parameters). The description doesn't need to add parameter semantics, so a baseline of 4 is appropriate as it doesn't introduce confusion or 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 action ('Get a list') and resource ('all supported blockchain chains'), making the purpose immediately understandable. It doesn't differentiate from sibling tools like 'gateway_get_evm_chains' or 'gateway_get_url', 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?

No guidance is provided on when to use this tool versus alternatives like 'gateway_get_evm_chains' or 'gateway_is_evm_chain'. The description only states what it does, not when it's appropriate, leaving the agent to infer usage context.

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

Related 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/tatumio/tatum-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server