Skip to main content
Glama

read.pool.list

Read-onlyIdempotent

List all Arcadia lending pools with key metrics: TVL, utilization, available liquidity, interest rate (borrow cost), and lending APY (lender yield). All rates are decimal fractions.

Instructions

List all Arcadia lending pools: TVL, utilization, available liquidity. Key fields: interest_rate = current borrow cost, lending_apy = lender yield. All rates are decimal fractions (1.0 = 100%, 0.06 = 6%). For APY history on a specific pool, use read.pool.info.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
chain_idNoChain ID: 8453 (Base), 130 (Unichain), or 10 (Optimism)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
poolsYes
context_notesNo

Implementation Reference

  • Handler function for the 'read.pool.list' tool. Calls api.getPools(chain_id), wraps the result in {pools: ...}, and returns it as both text and structuredContent. Handles empty results and errors.
    async ({ chain_id }) => {
      try {
        const result = await api.getPools(chain_id);
        if (Array.isArray(result) && result.length === 0) {
          const empty = {
            pools: [] as unknown[],
            context_notes: [`No lending pools found on chain ${chain_id}.`],
          };
          return {
            content: [{ type: "text" as const, text: JSON.stringify(empty, null, 2) }],
            structuredContent: empty,
          };
        }
        const wrapped = { pools: Array.isArray(result) ? result : [] };
        return {
          content: [{ type: "text" as const, text: JSON.stringify(wrapped, null, 2) }],
          structuredContent: wrapped,
        };
      } catch (err) {
        return {
          content: [
            {
              type: "text" as const,
              text: `Error: ${err instanceof Error ? err.message : String(err)}`,
            },
          ],
          isError: true,
        };
      }
    },
  • Registration of 'read.pool.list' tool via server.registerTool(). Defines annotations, description, inputSchema (chain_id), and outputSchema (PoolListOutput).
    export function registerPoolTools(server: McpServer, api: ArcadiaApiClient) {
      server.registerTool(
        "read.pool.list",
        {
          annotations: {
            title: "List Lending Pools",
            readOnlyHint: true,
            destructiveHint: false,
            idempotentHint: true,
            openWorldHint: true,
          },
          description:
            "List all Arcadia lending pools: TVL, utilization, available liquidity. Key fields: interest_rate = current borrow cost, lending_apy = lender yield. All rates are decimal fractions (1.0 = 100%, 0.06 = 6%). For APY history on a specific pool, use read.pool.info.",
          inputSchema: {
            chain_id: z.number().default(8453).describe(CHAIN_ID_DESCRIPTION),
          },
          outputSchema: PoolListOutput,
        },
        async ({ chain_id }) => {
          try {
            const result = await api.getPools(chain_id);
            if (Array.isArray(result) && result.length === 0) {
              const empty = {
                pools: [] as unknown[],
                context_notes: [`No lending pools found on chain ${chain_id}.`],
              };
              return {
                content: [{ type: "text" as const, text: JSON.stringify(empty, null, 2) }],
                structuredContent: empty,
              };
            }
            const wrapped = { pools: Array.isArray(result) ? result : [] };
            return {
              content: [{ type: "text" as const, text: JSON.stringify(wrapped, null, 2) }],
              structuredContent: wrapped,
            };
          } catch (err) {
            return {
              content: [
                {
                  type: "text" as const,
                  text: `Error: ${err instanceof Error ? err.message : String(err)}`,
                },
              ],
              isError: true,
            };
          }
        },
      );
  • PoolListOutput Zod schema: an object with 'pools' (array of unknown records) and optional 'context_notes' (array of strings).
    export const PoolListOutput = z.object({
      pools: z.array(z.record(z.unknown())),
      context_notes: z.array(z.string()).optional(),
    });
  • getPools() method on ArcadiaApiClient — sends GET request to '/pools' with chain_id parameter. This is the underlying API call used by the tool handler.
    async getPools(chainId: number) {
      return this.get<ApiListResponse>("/pools", { chain_id: chainId });
    }
  • Top-level registration of registerPoolTools (which includes read.pool.list) called from registerAllTools.
    registerAccountTools(server, api, chains);
    registerPoolTools(server, api);
    registerAssetTools(server, api);
Behavior4/5

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

Annotations already declare readOnlyHint, destructiveHint, and idempotentHint. The description adds that it lists all pools with no filtering, and explains decimal fraction output. No contradictions; adds useful behavioral context beyond annotations.

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 sentences, front-loaded with purpose and key fields, no redundant information. Every sentence adds value.

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?

Given the presence of an output schema and simple parameter, the description covers purpose, key field semantics, decimal format, and sibling reference. No gaps for a list tool.

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% for the single parameter chain_id, including chain IDs and default. The description adds no further parameter information, which is acceptable per guidelines (baseline 3).

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 'List all Arcadia lending pools' with specific fields (TVL, utilization, available liquidity). It distinguishes from sibling read.pool.info by directing users to that tool for APY history.

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

Usage Guidelines5/5

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

Explicitly provides when-to-use (list all pools) and when-not-to-use (for APY history on a specific pool, use read.pool.info). This is a clear alternative and exclusion.

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

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