Skip to main content
Glama

Search tokenized properties

search_properties
Read-only

Find tokenized real-estate listings across RealT, Lofty, Binaryx and Reental. Filter by platform, country, text, payout status or recent trading. Each row has the last traded price, issue price, yield with its basis, payout status and caveats.

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": "search_properties"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNoDefault last_trade (most recently traded first). 'yield' ranks listings whose distributions are being paid first, then those that are not, then off-plan projections.
limitNoDefault 20.
queryNoText matched against the address/title and location, e.g. 'Detroit' or 'Chase St'.
countryNoCountry name, e.g. 'United States', 'Spain'. Case-insensitive.
platformNoLimit to one platform. Omit for all four.
payout_statusNoregular = distributions arriving on schedule; stalled = overdue; not_started = not yet paying (e.g. under construction).
include_exitedNoInclude sold/redeemed and unlisted listings. Default false.
traded_within_daysNoOnly listings with an executed trade in this many days.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / platform / description
      Added value: +"Limit to one platform. Omit for all four."
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety and scope are covered. The description earnestly adds value beyond them by describing the returned row (last traded price, issue price, yield with its basis, payout status, caveats), which matters because there is no output schema — the 'yield with its basis' and 'caveats' notes warn the agent that yield figures are not directly comparable.

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, front-loaded with the purpose, then filtering, then return shape. No filler, and the return-shape sentence earns its space given the absence of an output schema.

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?

For an eight-parameter search tool with no output schema, the definition covers purpose, filter set, and result fields adequately. Minor gaps remain around maximum result size and whether results are paginated or a single capped page, but nothing essential 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 all eight parameters, including three enums, are documented in the schema itself. The description only restates the filter categories, adding no syntax, defaults, or interaction rules (e.g. combining query with country) beyond what the schema provides; 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: find tokenized real-estate listings, scoped to four named platforms. An agent immediately knows this is a filtered listing search, but the description never names a sibling (e.g. get_property for detail, get_recent_trades for trade history) to make the boundary explicit.

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

Usage Guidelines3/5

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

Names the available filters (platform, country, text, payout status, recent trading) which implies how to narrow a search, but gives no explicit when-to-use guidance or exclusions — e.g. whether to use this or get_recent_trades for trade-centric questions. Usage is inferable rather than stated.

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