Skip to main content
Glama
kukapay

chainlink-feeds-mcp

listSupportedFeeds

Retrieve all available blockchain networks and their corresponding price feed identifiers from Chainlink's decentralized oracle system.

Instructions

Returns a Markdown list of all supported chains and their price feed names

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the listSupportedFeeds tool. It generates a Markdown-formatted list of all supported chains and their available price feed names by iterating over the feedsData object.
    async () => {
      try {
        // Prepare Markdown list
        const markdownList = Object.keys(feedsData).map((chain) => {
          const feedNames = feedsData[chain].feeds.map((feed) => feed.name).join(',');
          return `- ${chain}: ${feedNames}`;
        }).join('\n');
    
        return {
          content: [{
            type: 'text',
            text: markdownList
          }]
        };
      } catch (error) {
        return {
          content: [{
            type: 'text',
            text: `Error: ${error.message}`
          }],
          isError: true
        };
      }
    }
  • Zod schema definition for the listSupportedFeeds tool, which requires no input parameters.
    const listSupportedFeedsSchema = z.object({}).describe('No parameters required');
  • index.js:231-259 (registration)
    Registration of the listSupportedFeeds tool via server.tool(), specifying the tool name, description, input schema, and handler function.
    server.tool(
      'listSupportedFeeds',
      'Returns a Markdown list of all supported chains and their price feed names',
      listSupportedFeedsSchema,
      async () => {
        try {
          // Prepare Markdown list
          const markdownList = Object.keys(feedsData).map((chain) => {
            const feedNames = feedsData[chain].feeds.map((feed) => feed.name).join(',');
            return `- ${chain}: ${feedNames}`;
          }).join('\n');
    
          return {
            content: [{
              type: 'text',
              text: markdownList
            }]
          };
        } catch (error) {
          return {
            content: [{
              type: 'text',
              text: `Error: ${error.message}`
            }],
            isError: true
          };
        }
      }
    );
Behavior3/5

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

With no annotations provided, the description carries the full burden. It discloses the output format (Markdown list) and scope (all supported chains and feed names), which is useful behavioral context. However, it lacks details on potential limitations like rate limits, error handling, or data freshness.

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 that front-loads the core action and output format with zero wasted words, making it easy to parse quickly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/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 annotations, no output schema), the description is complete enough for a read-only listing operation. It clearly states what is returned, though adding minor context like data source or update frequency could improve it further.

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%, so no parameter documentation is needed. The description appropriately focuses on output semantics, earning a baseline score of 4 for not introducing unnecessary complexity.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the specific action ('Returns') and the resource ('a Markdown list of all supported chains and their price feed names'), distinguishing it from siblings like 'getLatestPrice' (which fetches specific prices) and 'listSupportedChains' (which likely lists only chains without feed details).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage when needing a comprehensive list of chains and feeds, but does not explicitly state when to use this tool versus alternatives like 'listSupportedFeedsByChain' (which might filter by chain) or 'queryPriceByRound' (which queries specific data). No exclusions or prerequisites are mentioned.

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