Skip to main content
Glama

Get one tokenized property

get_property
Read-only

Full profile of one listing by its BrickTable id (from search_properties): price and issue price, yield with basis, payout status, tokens, holders and concentration, rent, ZIP-level home value and rent (US), recent trading, and caveats.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "get_property"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesBrickTable property id, e.g. 'lofty-01JGMSZ4NEGCFF8T8CEE5XXYQ7'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds a substantial inventory of what the response contains (price, yield basis, payout status, holders/concentration, rent, ZIP-level value, trading, caveats), which usefully sets expectations given there is no output schema. It does not address behavior on an unknown or stale id, or whether data is real-time.

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?

A single sentence, front-loaded with the object of the call, with zero filler. The long field enumeration is dense but each item carries informational value.

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 a one-parameter read-only lookup with full schema coverage and annotation-declared safety, the description is close to sufficient, and the field inventory compensates for the missing output schema. The residual gap is absence of any note on failures for invalid ids or on data currency.

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 single 'id' parameter already documents its format and gives a concrete example. The description's only added meaning is provenance ('from search_properties'), which is marginal beyond the schema.

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 and resource ('Full profile of one listing'), plus the keying mechanism ('by its BrickTable id') and the source of that id ('from search_properties'). An agent can distinguish this from the sibling search and trades tools without consulting any 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?

The parenthetical '(from search_properties)' establishes the prerequisite workflow, making it clear this tool is a second step after a search. It stops short of explicit exclusions, e.g. deferring trade history to get_property_trades, so the boundary against that sibling is left implicit.

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