THORChain MCP

List Pools

list_pools

Read-onlyIdempotent

Returns all active liquidity pools on THORChain with their balances, units, and status. Supports pagination with limit and offset parameters.

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_pools"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	Maximum number of results to return (default 100, max 1000)
`offset`	No	Number of results to skip for pagination

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 21, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, open-world), so the description's job is to add operational detail. It does: it discloses that only 'active' pools are returned and names the per-record fields, which matters because there is no output schema. It does not state ordering, totals, or whether inactive pools are retrievable elsewhere.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with what is returned, then the pagination note. Nothing is wasted, though the second sentence largely echoes parameters the schema already fully documents.

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?

For a simple two-parameter list tool with no output schema, the description carries the important missing piece by enumerating the returned fields and the active-only filter. Ordering and page-size default behavior are left to the schema and are acceptable omissions.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% and both parameters are documented there, including the default 100 and max 1000. The description only restates that pagination is supported via limit and offset, adding no format or interaction detail beyond the schema, so the baseline 3 applies.

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?

States a specific verb and resource ('Returns all active liquidity pools on THORChain') plus the content of each record (balances, units, status). The word 'all' distinguishes it in spirit from sibling get_pool, but no sibling is named explicitly, so the differentiation is implied rather than stated.

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?

Usage is implied by 'all active ... pools' versus the singular get_pool and the aggregate get_pool_stats, but the description never says when to choose this over those siblings, nor any prerequisites or exclusions. An agent can infer the routing, but must do the work itself.

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

All THORChain MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?