TokenBank — tokenized real-world assets

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

TableJSON 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

TableJSON 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.5/5.0

Behavior4/5

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

Annotations already declare a safe, idempotent, non-destructive read, so the bar is lower. The description still adds real context: default tier, what imported rows do and do not carry, and that output is compact rather than full records. It stops short of describing pagination or result ordering.

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, zero filler, with the default-tier scoping and the sibling pointer front-loaded. Every sentence carries information an agent needs to route or invoke correctly.

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-value detail isn't required; the description still flags compact records and points to get_product_details for the full record. Combined with a fully documented 7-parameter schema, nothing needed for correct invocation is missing.

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%, and the description largely restates the tier semantics already present in the tier parameter's schema text. It reinforces intent but adds little syntax or format meaning beyond the schema, so the baseline 3 is appropriate.

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 (search/filter) plus resource (TokenBank yield instruments) and distinguishes itself from get_product_details, which it explicitly names as the fuller-record alternative. The tier behavior is described up front so an agent can tell what corpus it queries.

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 explicit when-to-use rules: curated tier for yield/minimum/risk questions, imported tier only for identity questions, and get_product_details for full records. The exclusions ('never for yield rankings') are rare and valuable routing guidance.

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?