Skip to main content
Glama

read.asset.list

Read-onlyIdempotent

List supported collateral assets on Arcadia, filterable by symbol substring. Returns address, symbol, decimals, and type.

Instructions

List supported collateral assets on Arcadia. Returns compact list (address, symbol, decimals, type). Use search to filter by symbol substring. For USD prices, use read.asset.prices.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
searchNoFilter assets by symbol (case-insensitive substring match)
chain_idNoChain ID: 8453 (Base), 130 (Unichain), or 10 (Optimism)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
totalYes
assetsYes

Implementation Reference

  • The main handler function for the read.asset.list tool. Calls api.getAssets(), normalizes the response into a uniform array, optionally filters by symbol search, and returns a JSON result with total count and asset list.
    async ({ search, chain_id }) => {
      try {
        const raw = await api.getAssets(chain_id);
        const obj = raw as Record<string, unknown>;
        const allAssets = (Array.isArray(raw) ? raw : (obj.assets ?? obj.data ?? [])) as Record<
          string,
          unknown
        >[];
        let assets = allAssets.map((a) => ({
          address: a.address ?? a.asset_address,
          symbol: a.name ?? a.symbol ?? a.asset_symbol,
          decimals: a.decimals,
          type: a.standard ?? a.asset_type ?? a.type,
        }));
        if (search) {
          const q = search.toLowerCase();
          assets = assets.filter((a) => ((a.symbol as string) ?? "").toLowerCase().includes(q));
        }
        const result = { total: assets.length, assets };
        return {
          content: [{ type: "text" as const, text: JSON.stringify(result, null, 2) }],
          structuredContent: result,
        };
      } catch (err) {
        return {
          content: [
            {
              type: "text" as const,
              text: `Error: ${err instanceof Error ? err.message : String(err)}`,
            },
          ],
          isError: true,
        };
      }
    },
  • Tool registration with annotations, input schema (search optional string, chain_id number defaulting to 8453), and output schema reference to AssetListOutput.
    "read.asset.list",
    {
      annotations: {
        title: "List Supported Assets",
        readOnlyHint: true,
        destructiveHint: false,
        idempotentHint: true,
        openWorldHint: true,
      },
      description:
        "List supported collateral assets on Arcadia. Returns compact list (address, symbol, decimals, type). Use search to filter by symbol substring. For USD prices, use read.asset.prices.",
      inputSchema: {
        search: z
          .string()
          .optional()
          .describe("Filter assets by symbol (case-insensitive substring match)"),
        chain_id: z.number().default(8453).describe(CHAIN_ID_DESCRIPTION),
      },
      outputSchema: AssetListOutput,
  • Tool registration via server.registerTool, called from registerAssetTools() function.
    server.registerTool(
      "read.asset.list",
      {
        annotations: {
          title: "List Supported Assets",
          readOnlyHint: true,
          destructiveHint: false,
          idempotentHint: true,
          openWorldHint: true,
        },
        description:
          "List supported collateral assets on Arcadia. Returns compact list (address, symbol, decimals, type). Use search to filter by symbol substring. For USD prices, use read.asset.prices.",
        inputSchema: {
          search: z
            .string()
            .optional()
            .describe("Filter assets by symbol (case-insensitive substring match)"),
          chain_id: z.number().default(8453).describe(CHAIN_ID_DESCRIPTION),
        },
        outputSchema: AssetListOutput,
      },
      async ({ search, chain_id }) => {
        try {
          const raw = await api.getAssets(chain_id);
          const obj = raw as Record<string, unknown>;
          const allAssets = (Array.isArray(raw) ? raw : (obj.assets ?? obj.data ?? [])) as Record<
            string,
            unknown
          >[];
          let assets = allAssets.map((a) => ({
            address: a.address ?? a.asset_address,
            symbol: a.name ?? a.symbol ?? a.asset_symbol,
            decimals: a.decimals,
            type: a.standard ?? a.asset_type ?? a.type,
          }));
          if (search) {
            const q = search.toLowerCase();
            assets = assets.filter((a) => ((a.symbol as string) ?? "").toLowerCase().includes(q));
          }
          const result = { total: assets.length, assets };
          return {
            content: [{ type: "text" as const, text: JSON.stringify(result, null, 2) }],
            structuredContent: result,
          };
        } catch (err) {
          return {
            content: [
              {
                type: "text" as const,
                text: `Error: ${err instanceof Error ? err.message : String(err)}`,
              },
            ],
            isError: true,
          };
        }
      },
    );
  • API client helper that fetches the list of assets from the /assets endpoint.
    async getAssets(chainId: number) {
      return this.get("/assets", { chain_id: chainId });
    }
  • Zod output schema for the asset list response: total count and array of assets with address, symbol, decimals, and type fields.
    export const AssetListOutput = z.object({
      total: z.number(),
      assets: z.array(
        z.object({
          address: z.unknown(),
          symbol: z.unknown(),
          decimals: z.unknown(),
          type: z.unknown(),
        }),
      ),
    });
Behavior4/5

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

Annotations already indicate read-only, idempotent, and non-destructive behavior. The description adds value by specifying the return fields (address, symbol, decimals, type) and the search filtering behavior, going 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: first states main function and output, second provides usage guidance. No wasted words; front-loaded with purpose.

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 list tool with fully documented schema and annotations, the description is adequate. It mentions output fields and directs to alternative tool. Could mention pagination or ordering, but not critical given low complexity.

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%, so baseline is 3. The description reiterates the search parameter's purpose but does not add new meaning beyond the schema's description for either parameter.

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 the tool lists supported collateral assets on Arcadia and mentions the return fields (address, symbol, decimals, type). It distinguishes from the sibling read.asset.prices by directing users there for USD prices.

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?

Provides guidance on using the search parameter to filter by symbol and explicitly directs users to read.asset.prices for USD prices. Lacks explicit 'when not to use' but offers a clear alternative.

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