Skip to main content
Glama

AINDEX

Tokens AINDEX can identify and price

list_assets
Read-only

The tokens AINDEX can identify and price: every Robinhood stock token and fund (ETF) token, USDG, and the other tokens AINDEX prices, with price, source, dividend multiplier, halted state, verification, and pool depth (the dollars that move the token's best pool 1%, from liquidity actually within 1% of its price, the thinner of buying and selling).

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
kindNostock = companies, fund = ETFs and trusts, token = everything else.all
sortNodepth
limitNo
queryNoFilter by ticker, name or fund category (for example 'treasury', 'semiconductor', 'NVDA').
verifiedOnlyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior4/5

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

Annotations only cover safety (readOnlyHint=true, openWorldHint=false), and the description goes well beyond them by enumerating the returned fields (price, source, dividend multiplier, halted state, verification, pool depth) and defining the non-obvious pool-depth metric as the dollars that move the best pool 1%, measured on the thinner side. It omits ordering behavior, pagination/limit semantics, and the fact that results are filtered by default.

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?

A single front-loaded sentence that puts the covered universe first and the returned fields second, with no filler. The deeply nested parenthetical defining pool depth is dense but earns its place because that metric is otherwise opaque.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description correctly takes on the burden of describing return fields and does so thoroughly. However, for a filtered, sorted, limit-capped list tool it leaves out default-filter behavior and pagination, which are exactly the details an agent needs to avoid misreading a partial or filtered result as the full universe.

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

Parameters2/5

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

Schema coverage is only 40% across five parameters, and the description adds no parameter meaning whatsoever. Critically, it never mentions that verifiedOnly defaults to true, so the default call silently excludes unverified tokens, nor does it explain sort or limit behavior beyond the bare enum/integer in the schema.

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?

The description precisely delimits the resource: every Robinhood stock token and fund (ETF) token, USDG, and other tokens AINDEX prices, plus the per-token attributes returned. It is clear what the call yields, though it opens with a near-verbatim restatement of the title and never contrasts itself with search_tokens, discover_tokens, or get_asset.

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

Usage Guidelines2/5

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

There is no when-to-use guidance at all: nothing says to prefer this for a full catalog versus search_tokens for a lookup or get_asset for a single token. The agent must infer routing from the sibling names alone, which the description does nothing to support.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources