Skip to main content
Glama

Executed trades for one property

get_property_trades
Read-only

Recorded secondary-market fills for one listing over the last 90 days, newest first, with quantity, price, settlement currency, USD value and a block-explorer link. Includes a summary (fill count, USD volume, volume-weighted price). The full history back to 2022 is available as a data license at bricktable.co/data.

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": {
      "property_id": "<property_id>"
    },
    "name": "get_property_trades"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoLook-back window, up to 90 days on the free server. Default 90.
limitNoMax fills returned (newest first). Default 50. The summary covers the whole window.
property_idYesBrickTable property id from search_properties, e.g. 'realt-...' or 'lofty-...'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / property_id / description
      Added value: +"BrickTable property id from search_properties, e.g. 'realt-...' or 'lofty-...'."
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations declare readOnlyHint=true and openWorldHint=false, and the description is fully consistent with a safe read. It adds genuinely useful behavioral context beyond the annotations: the 90-day server-side cap, the 2022-onward history being available only as a licensed dataset, and the fact that the summary aggregates over the whole window rather than the returned page.

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, no padding: scope and ordering first, payload contents second, then the important limit on historical depth. Even the pointer to the licensed full history earns its place by telling the agent when to stop and look elsewhere.

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 no output schema, the description properly compensates by enumerating returned fields (quantity, price, settlement currency, USD value, explorer link) and the summary triple. It stops short of covering pagination beyond limit or error behavior for an unknown property_id, which is a modest gap for a read-only listing tool.

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 days, limit and property_id are already documented in the schema, including defaults, bounds and the note that the summary covers the whole window. The description adds only the "newest first" ordering, which the schema already states for limit, so 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 ("Recorded secondary-market fills for one listing") plus the time scope (last 90 days) and ordering (newest first). The "one listing" framing implicitly separates it from the multi-property get_recent_trades sibling, but that sibling is never named, so differentiation is inferential rather than 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?

Usage is implied by the single-listing scope and the 90-day free-server limit, which tells the agent when this tool is insufficient (older history requires the data license). There is, however, no explicit when-to-use versus get_recent_trades or get_property, and no statement that property_id must come from search_properties in the description itself.

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