Skip to main content
Glama
Coinversaa

Coinversaa Pulse

Official
by Coinversaa
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

list_asset

Look up an asset by name or synonym to retrieve its trading venues, collateral tokens, open interest per venue, and synonyms list.

Instructions

Lookup one asset by canonical name or synonym. Returns every venue it trades on, collateral tokens, open interest per venue, and synonyms list. Accepts both canonical names (GOLD, BTC) and synonyms (PAXG, XAUT) — the server resolves them. Use when the user mentions a specific asset and you need its venue availability.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
useToonFormatNoReturn data in compact toon format (default: true). Set to false for standard JSON.
canonicalYesCanonical asset name or synonym. Examples: 'GOLD', 'PAXG', 'BTC', 'SILVER', 'HYPE'. The server resolves synonyms to canonical.

Implementation Reference

  • src/index.ts:310-322 (registration)
    Registration of the 'list_asset' tool via server.registerTool(). The tool is registered with input schema requiring 'canonical' (asset name or synonym) and optional 'useToonFormat'. It calls the API endpoint /assets/{canonical}.
    if (shouldRegister("list_asset")) server.registerTool(
  "list_asset",
  {
    description: "Lookup one asset by canonical name or synonym. Returns every venue it trades on, collateral tokens, open interest per venue, and synonyms list. Accepts both canonical names (GOLD, BTC) and synonyms (PAXG, XAUT) — the server resolves them. Use when the user mentions a specific asset and you need its venue availability.",
    inputSchema: {
      useToonFormat: useToonFormatSchema,
      canonical: z.string().min(1).max(40).describe("Canonical asset name or synonym. Examples: 'GOLD', 'PAXG', 'BTC', 'SILVER', 'HYPE'. The server resolves synonyms to canonical."),
    },
  },
  async ({ useToonFormat, canonical }) => {
    return toolResult(await callAPI(useToonFormat, `/assets/${encodeURIComponent(canonical)}`));
  }
);
  • src/index.ts:319-321 (handler)
    The handler function for 'list_asset'. It receives 'useToonFormat' and 'canonical', then calls the API at `/assets/{canonical}` using the callAPI helper. The canonical parameter is URL-encoded to handle special characters.
    async ({ useToonFormat, canonical }) => {
  return toolResult(await callAPI(useToonFormat, `/assets/${encodeURIComponent(canonical)}`));
}
  • src/index.ts:313-318 (schema)
    Input schema for 'list_asset'. Defines two parameters: 'useToonFormat' (optional boolean, defaults to true) and 'canonical' (required string, 1-40 chars) for the asset name or synonym.
      description: "Lookup one asset by canonical name or synonym. Returns every venue it trades on, collateral tokens, open interest per venue, and synonyms list. Accepts both canonical names (GOLD, BTC) and synonyms (PAXG, XAUT) — the server resolves them. Use when the user mentions a specific asset and you need its venue availability.",
  inputSchema: {
    useToonFormat: useToonFormatSchema,
    canonical: z.string().min(1).max(40).describe("Canonical asset name or synonym. Examples: 'GOLD', 'PAXG', 'BTC', 'SILVER', 'HYPE'. The server resolves synonyms to canonical."),
  },
},

Tool Definition Quality

A4.6/5.0
Behavior4/5

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

No annotations provided, but the description discloses that the server resolves synonyms to canonical names and lists the returned data (venues, collateral, open interest, synonyms). It does not explicitly state read-only nature, but it's implied. Good transparency for a lookup tool.

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?

Three sentences: first states purpose and return, second explains input acceptance, third gives usage guidance. No redundancy, 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?

No output schema, but description explicitly lists return fields (venues, collateral, OI, synonyms). For a single-asset lookup tool, it covers all necessary aspects: input, resolution, output, and when to use.

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

Parameters5/5

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

Schema coverage is 100%, and the description adds value by providing example values for 'canonical' ('GOLD', 'PAXG', 'BTC') and explaining resolution behavior. For 'useToonFormat', it clarifies compact vs. standard JSON format.

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?

Clearly states 'Lookup one asset by canonical name or synonym' and lists return fields, distinguishing it from sibling tools like 'list_assets' (plural) and 'list_markets'.

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?

Explicitly says 'Use when the user mentions a specific asset and you need its venue availability.' This is a clear usage context, though it does not explicitly state when not to use it. The sibling differentiation is implied.

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

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