Skip to main content
Glama

List swappable assets

list_assets
Read-onlyIdempotent

Find exact asset IDs and supported chains for 340+ tokens across 40+ chains, filtering by chain or symbol, so you can confirm a token ID or see every chain that supports it before quoting or swapping.

Instructions

Search the 340+ assets on 40+ chains that Shieldz Swap can route and return their exact asset ids. Use it when you are unsure of an id or which chains support a token (e.g. every chain that has USDC). Skip it for common native coins: get_quote and create_swap already accept shorthand like ZEC.ZEC or BTC.BTC. With no filters it also returns the list of chain codes. Read-only; the list is cached for 60 seconds.

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

Input Schema

NameRequiredDescriptionDefault
chainNoExact chain code filter, e.g. ETH, BASE, ARB, OP, POL, BSC, SOL, BTC, ZEC, TRON, NEAR. Leave empty for all chains.
limitNoMaximum assets to return (1-100, default 40). Verified assets come first.
searchNoCase-insensitive symbol or asset id fragment, e.g. "usdc", "zec", "0x8335".

Output Schema

NameRequiredDescriptionDefault
assetsYesMatching assets, verified first.
chainsNoAll chain codes; only present when no filter was given.
total_matchesYesHow many assets matched before the limit.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description still adds real context beyond them: the list is cached for 60 seconds (staleness risk) and an unfiltered call also returns the list of chain codes. It does not discuss pagination or result ordering beyond the schema's 'verified assets come first'.

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?

Four short sentences, front-loaded with purpose, then usage, then the skip case, then behavior. Every sentence carries information, though 'Read-only' largely restates the readOnlyHint annotation and could be dropped.

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?

An output schema exists, so return values need no explanation. The description covers scale, filtering intent, default behavior, caching, and sibling alternatives — everything an agent needs to call this correctly.

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 all three parameters (chain, limit, search) are already documented with examples and defaults. The description adds only the unfiltered-call behavior ('with no filters it also returns the list of chain codes'), which is a default-behavior note rather than parameter semantics. Baseline 3 applies when the schema does the heavy lifting.

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 ('Search the 340+ assets on 40+ chains that Shieldz Swap can route and return their exact asset ids'), plus the scale of the catalog. It explicitly distinguishes itself from get_quote and create_swap, so an agent can pick it without opening any schema.

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?

Gives both directions: use it 'when you are unsure of an id or which chains support a token (e.g. every chain that has USDC)', and skip it 'for common native coins' because get_quote and create_swap accept shorthand like ZEC.ZEC or BTC.BTC. The alternative tools are named with the condition that selects them.

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