Skip to main content
Glama
Sign In
fibx

fibx

Official
by Fibrous-Finance
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

List Tokens

list_tokens
Read-onlyIdempotent

Retrieve supported tokens on a specified chain with symbol, name, address, decimals, and known USD prices. Use it to discover which tokens Fibrous can route before quoting or swapping.

Instructions

List the tokens Fibrous supports on a chain, with symbol, name, address, decimals and USD price where known.

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

Input Schema

NameRequiredDescriptionDefault
chainNoChain to list tokens forbase

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.10.2

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description still adds real value by enumerating the returned fields and qualifying USD price with 'where known', warning the agent that price may be absent for some tokens.

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?

One front-loaded sentence with no wasted words; the resource and its returned fields are stated immediately.

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 one-parameter read tool with full schema coverage and clear annotations, the description covers purpose and return shape adequately. The only minor gap is not stating whether the default chain is assumed when omitted, which the schema already handles.

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?

The single chain parameter is fully described in the schema with an enum of base/hyperevm/monad and a default of base, so the schema does all the work. The description only restates 'on a chain' without adding format or behavioral nuance.

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?

Specific verb (List) plus resource (tokens) scoped to a chain, and it names the returned attributes. It is distinguishable from siblings like get_balance or swap_tokens, though it doesn't explicitly contrast itself with them.

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 rather than stated: an agent can infer this is the discovery call before quoting or swapping, but there is no explicit when-to-use or when-not-to-use guidance and no named alternative.

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

Deploy Server

Other Tools