Skip to main content
Glama

CHAIN_LIST

Retrieve available blockchain networks for decentralized exchange operations, enabling users to identify supported chains for token swaps and transactions.

Instructions

Get chain list

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function that executes the CHAIN_LIST tool, returning a hardcoded JSON string of supported chain names.
    export const chainList = async () => {
    	const chains = [ 'bsc', 'eth', 'polygon', 'fantom', 'avax', 'arbitrum', 'xdai', 'moonriver', 'optimism', 'aurora', 'cronos', 'harmony', 'aptos', 'near', 'metis', 'kava', 'celo', 'klaytn',
    		'zksync', 'polygon_zkevm', 'linea', 'telos', 'scroll', 'base', 'mantle', 'opbnb', 'manta', 'blast', 'mode', 'merlin', 'rootstock', 'sei', 'gravity', 'ape', 'sonic', 'sui', 'bera', 'uni', 'flare',
    		'monad', 'swell', 'hyperevm', 'plume', 'tac', 'plasma' ];
    	return JSON.stringify(chains, null, 2);
    };
  • src/tools/index.ts:5-9 (registration)
    The registration of the CHAIN_LIST tool in the tools export, linking to the handler and defining metadata.
    chainList: {
    	name: "CHAIN_LIST",
    	description: "Get chain list",
    	execute: chainExecute.chainList
    },
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. 'Get chain list' implies a read-only operation, but it fails to detail any behavioral traits such as rate limits, authentication needs, or what the output entails (e.g., format, data structure). This leaves significant gaps in understanding how the tool behaves.

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 extremely concise with just three words, front-loading the key action ('Get') and resource ('chain list'). There is no wasted language or redundancy, making it efficiently structured for its minimal content.

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 does not explain what a 'chain list' returns (e.g., a list of blockchain networks, their IDs, or configurations), leaving the agent without necessary context to understand the tool's output or its utility compared to siblings.

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 input schema coverage is 100%, so there are no parameters to document. The description does not need to add parameter semantics, and it appropriately avoids unnecessary details, aligning with the baseline expectation for a parameterless tool.

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

Purpose2/5

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

The description 'Get chain list' is a tautology that essentially restates the tool name 'CHAIN_LIST' without adding meaningful clarification. While it indicates a retrieval action ('Get'), it doesn't specify what a 'chain list' contains or how it differs from sibling tools like DEX_LIST or TOKEN_LIST, leaving the purpose vague.

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

Usage Guidelines1/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. The description lacks context about its role relative to siblings such as DEX_LIST or TOKEN_LIST, and there are no explicit instructions on prerequisites or exclusions, making it unclear when this tool is appropriate.

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/openocean-finance/openocean-mcp'

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