TokenBank — tokenized real-world assets

Search RealT properties

search_realt_properties

Read-onlyIdempotent

Drill into the RealT portfolio: the individual tokenized US rental properties behind the REALT entry, each with its own net rental yield (computed as annual net rent / tokenized property value), token price, monthly rent and occupancy. Use this when someone asks which specific tokenized property to buy, or for the yield/price spread within one issuer.

Input Schema

Name	Required	Description
`city`	No	City name, e.g. Detroit, Cleveland, Chicago
`sort`	No	Sort by net yield (default), token price (cheapest first) or monthly rent
`limit`	No	Max results (default 20)
`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.
`rented_only`	No	Only properties with at least one rented unit (default true)
`min_yield_pct`	No	Minimum net rental yield in percent
`max_token_price_usd`	No	Maximum price per token in USD

Output Schema

Name	Required	Description
`issuer`	Yes
`results`	No
`nextOffset`	No	Pass as offset to fetch the next page; absent when there is no more
`portfolioUrl`	No
`snapshotDate`	No
`totalMatching`	Yes
`portfolioTotal`	No
`medianNetYieldPct`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedSep 29, 2026

addedOutput schema / properties / portfolioUrl
```
Added value: +{
+  "type": "string"
+}
```

removedOutput schema / properties / properties

Removed value: -{
-  "items": {
-    "type": "object"
-  },
-  "type": "array"
-}

addedOutput schema / properties / results

Added value: +{
+  "items": {
+    "type": "object"
+  },
+  "type": "array"
+}

First observedSep 16, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so the safety profile is covered. The description adds useful domain context by defining net rental yield (annual net rent / tokenized property value), but says nothing about pagination behavior or result scope beyond that.

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?

Two sentences, zero filler, with the identity of the tool front-loaded and the usage cue second. Every clause carries information.

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?

An output schema exists, so return values need not be restated, and the description explains the headline computed metric. The only small gap is that pagination is left entirely to the schema rather than hinted at in prose, but nothing needed to call the tool correctly 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 coverage is 100%, so the schema already documents every parameter including the offset/nextOffset walk and defaults. The description only alludes to yield/price spread and adds no syntax or format detail beyond the schema. Baseline 3 applies.

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?

Specific verb ('drill into') plus precise resource ('individual tokenized US rental properties behind the REALT entry'), and it enumerates the distinguishing fields (net yield, token price, monthly rent, occupancy). An agent can separate this from the issuer-level or generic product siblings 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 Guidelines4/5

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

Gives an explicit trigger: 'when someone asks which specific tokenized property to buy, or for the yield/price spread within one issuer.' That implicitly points away from the broader aggregate/view tools, but it never names the alternative or states when not to use it.

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?