Skip to main content
Glama

get-chains

Retrieve configured blockchain networks for secure AI-powered interactions through MetaMask wallet without exposing private keys.

Instructions

Get the configured chains

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The execute handler for the 'get-chains' tool. It retrieves configured chains using wagmi's getChains function with the wagmiConfig and returns the JSON-stringified result as text content.
    execute: async () => {
      const result = getChains(wagmiConfig)
      return {
        content: [
          {
            type: "text",
            text: JSONStringify(result),
          },
        ],
      }
    },
  • Zod schema defining the input parameters for the 'get-chains' tool (empty object, no parameters).
    parameters: z.object({}),
  • The registerGetChainsTools function that defines and registers the 'get-chains' MCP tool with the FastMCP server, including name, description, schema, and handler.
    export function registerGetChainsTools(server: FastMCP): void {
      server.addTool({
        name: "get-chains",
        description: "Get the configured chains",
        parameters: z.object({}),
        execute: async () => {
          const result = getChains(wagmiConfig)
          return {
            content: [
              {
                type: "text",
                text: JSONStringify(result),
              },
            ],
          }
        },
      });
    };
  • The call to registerGetChainsTools during server initialization, importing all tool registrations from './tools/index.js'.
    registerGetChainsTools(server);
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states 'Get the configured chains' but doesn't clarify if this is a read-only operation, what format the output is in, or any constraints like rate limits. For a tool with zero annotation coverage, this is insufficient.

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, clear sentence with no wasted words. It's front-loaded and efficiently conveys the core action, making it easy to parse without unnecessary elaboration.

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 no annotations and no output schema, the description is incomplete. It doesn't explain what 'configured chains' means, the return format, or any behavioral traits. For a tool in a complex blockchain context with many siblings, more detail is needed to guide the agent effectively.

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 input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description doesn't add parameter details, which is appropriate, but it could have mentioned any implicit context (e.g., no filtering options). Baseline is 4 for zero parameters.

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 ('Get') and resource ('configured chains'), making the purpose understandable. However, it doesn't differentiate from sibling tools like 'get-chain-id' or 'get-block', which also retrieve chain-related information, so it doesn't fully distinguish its specific scope.

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 'get-chain-id' or 'get-block'. The description lacks context about its specific use case, such as retrieving all configured chains versus single-chain details, leaving the agent without clear usage instructions.

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/Xiawpohr/mcpilot'

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