Skip to main content
Glama

List supported chains

list_chains
Read-onlyIdempotent

List the blockchains check_token supports, with the chain key to pass, chain id, whether a live honeypot sell simulation is available, and which data sources are used. Free, no quota.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_chains"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the readOnly/idempotent/destructive annotations, the description discloses cost and rate-limit behavior ('Free, no quota') and describes the shape of what comes back — chain key, chain id, live honeypot sell simulation availability, and data sources. For a tool with no output schema, this return-content disclosure is meaningful added context the annotations do not provide.

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?

Two short sentences: the capability and its return contents first, the cost/limit note last. No redundant restatement of the title and nothing that could be cut.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter, read-only listing with no output schema, the description covers purpose, response contents, quota behavior, and its relationship to check_token. There is no remaining question an agent would need answered before calling it.

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 takes no parameters, so the baseline is 4 and there is nothing for the description to disambiguate. It uses the space instead to explain what the response fields mean, which is a reasonable substitute.

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?

States a specific verb and resource ('List the blockchains') and scopes it precisely to what check_token supports, so the agent immediately knows this is the enumeration endpoint for the sibling tool. It also enumerates the returned fields (chain key, chain id, honeypot simulation flag, data sources), making the tool's purpose concrete rather than generic.

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

Usage Guidelines4/5

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

The phrase 'the chain key to pass' implicitly tells the agent this is the lookup step that produces the identifier needed by check_token, which is clear routing guidance. There is no explicit when-to-use statement or alternative named, so it falls short of the 5-level 'use X instead of Y' explicitness, but a zero-parameter static list needs little more.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources