TokenBank — tokenized real-world assets

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

TableJSON 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

TableJSON 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

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered. The description adds the net-yield definition (annual net rent / tokenized property value), which clarifies data semantics, but says nothing about rate limits, freshness, or auth needs. With annotations carrying the safety profile, a 3 is appropriate.

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?

Two sentences, front-loaded with what the tool returns and followed by the usage condition. Dense but no wasted filler; only the parenthetical formula slows the read slightly.

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?

With an output schema present, return values need no explanation, and all seven optional parameters are covered. The description supplies the scope and yield definition needed to use it correctly; only sibling routing is left implicit.

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 every one of the seven parameters is documented inline, including sort order defaults and the offset/nextOffset pagination pattern. The description adds no parameter meaning beyond this, so the baseline 3 applies.

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?

States a specific verb and resource: drilling into the RealT portfolio for individual tokenized US rental properties, and enumerates the returned attributes (yield, token price, rent, occupancy). It establishes the position in the hierarchy ('behind the REALT entry', 'within one issuer') but does not name a sibling it should be chosen over.

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 a clear triggering context: 'when someone asks which specific tokenized property to buy, or for the yield/price spread within one issuer.' This is real usage guidance, though it names no alternative tool and states no exclusions or prerequisites.

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?