Skip to main content
Glama
kukapay

chainlink-feeds-mcp

listSupportedChains

Retrieve all supported blockchain networks for Chainlink price feeds to verify compatibility before querying data.

Instructions

Returns a comma-separated list of all supported blockchain networks

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler function for the 'listSupportedChains' tool. It extracts chain names from feedsData JSON using Object.keys and joins them into a comma-separated string, returning it as text content. Includes error handling.
    async () => {
      try {
        // Get all chain names as comma-separated string
        const chains = Object.keys(feedsData).join(',');
    
        return {
          content: [{
            type: 'text',
            text: chains
          }]
        };
      } catch (error) {
        return {
          content: [{
            type: 'text',
            text: `Error: ${error.message}`
          }],
          isError: true
        };
      }
    }
  • Zod schema definition for the 'listSupportedChains' tool, specifying no input parameters are required.
    const listSupportedChainsSchema = z.object({}).describe('No parameters required');
  • index.js:161-186 (registration)
    Registration of the 'listSupportedChains' tool via server.tool method, providing name, description, schema, and inline handler function.
    server.tool(
      'listSupportedChains',
      'Returns a comma-separated list of all supported blockchain networks',
      listSupportedChainsSchema,
      async () => {
        try {
          // Get all chain names as comma-separated string
          const chains = Object.keys(feedsData).join(',');
    
          return {
            content: [{
              type: 'text',
              text: chains
            }]
          };
        } catch (error) {
          return {
            content: [{
              type: 'text',
              text: `Error: ${error.message}`
            }],
            isError: true
          };
        }
      }
    );
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 states the return format ('comma-separated list') but lacks details on error handling, rate limits, authentication needs, or whether the list is static or dynamic. This is a significant gap 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 zero waste. It's front-loaded with the core action and resource, making it easy to parse quickly.

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 adequate but has clear gaps. It explains what the tool does but lacks behavioral context and usage guidelines. For a read-only list tool, this is minimally viable but could be more helpful.

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% (though empty). The description doesn't need to add parameter details, so it meets the baseline for no parameters. It does mention the output format ('comma-separated list'), which adds slight value beyond the schema.

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 verb ('Returns') and resource ('comma-separated list of all supported blockchain networks'), making the purpose unambiguous. However, it doesn't explicitly differentiate from sibling tools like 'listSupportedFeeds' or 'listSupportedFeedsByChain', which also list things but with different scopes.

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 doesn't mention prerequisites, context for usage, or compare it to siblings like 'listSupportedFeeds' or 'listSupportedFeedsByChain', leaving the agent to infer usage based on tool names 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/kukapay/chainlink-feeds-mcp'

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