TokenBank — tokenized real-world assets

Search yield products

search_yield_products

Read-onlyIdempotent

Search and filter TokenBank's instruments for earning yield with crypto. Searches the CURATED tier by default (the rows that state a yield, minimum and risk); pass tier to reach the imported issuer-catalogue rows (tokenized treasuries, yield stablecoins, gold, real estate, tokenized stocks, staking, DeFi/CeFi earn, alternative funds). Returns compact records; use get_product_details for the full record.

Input Schema

Name	Required	Description
`tier`	No	Which tier to search. Default "curated": the instruments that state a yield, minimum and risk — the only ones that can answer "what does this pay". "imported" and "all" reach the issuer-catalogue rows, which carry identity and classification only. Use them for identity questions ("is X tokenized"), never for yield rankings.
`limit`	No	Max results (default 20)
`query`	No	Free-text match on name, ticker, issuer or type
`offset`	No	Skip this many matches before returning. Use the nextOffset from the previous answer to walk the whole set; its absence means you reached the end.
`pillar`	No	Limit to one category pillar
`max_risk`	No	Maximum risk on a 1-5 scale (1=very low, 3=medium, 5=high)
`min_yield_pct`	No	Minimum headline yield in percent

Output Schema

Name	Required	Description
`tier`	No
`count`	Yes	Rows returned
`results`	Yes
`nextOffset`	No	Pass as offset to fetch the next page; absent when there is no more
`totalMatching`	Yes	Rows that matched before the limit

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 2, 2026

removedInput schema / properties / eu_only

Removed value: -{
-  "description": "Only instruments available to EU investors",
-  "type": "boolean"
-}

First observedSep 16, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's added value is the tier behavior: curated rows carry yield/minimum/risk, imported rows carry identity/classification only. That is genuinely useful beyond the annotations, though the summary character of results ('compact records') is only lightly explained.

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?

Three front-loaded sentences; the default-tier constraint and the sibling pointer are never buried. Slight redundancy with the schema's own tier description, but no wasted sentences.

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 not be restated; the description still characterizes results as compact and routes to get_product_details for the full record. With 100% schema coverage and full annotations, an agent has everything needed 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 the schema already documents tier, offset/nextOffset paging, risk scale and limit semantics. The description reinforces the default-tier behavior but adds no syntax or format meaning beyond what the schema states.

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 and filter TokenBank's instruments for earning yield') plus the scope of the default result set. It also names the sibling used for full records (get_product_details), so the agent can separate it from alternatives without opening a 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?

Explicitly says the curated tier is the default and is the only one that answers yield questions, while imported/all are for identity questions and 'never for yield rankings.' The alternative (get_product_details) is named with its condition of use.

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

All TokenBank — tokenized real-world assets tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?