Skip to main content
Glama

Realtors Dashboard

Get published NYC comparable sales

get_nyc_property_comps
Read-onlyIdempotent

Read the current published comparable sale set for a verified NYC property or condo unit. Scores and adjusted amounts describe the comparable model.

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_nyc_property_comps"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesExact published property ID, condo unit BBL, or condo unit slug
limitNoMaximum records to return
offsetNoNumber of records to skip

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description's only added behavioral context is that scores and adjusted amounts describe the comparable model, which clarifies the nature of the returned data but not error cases, empty-result behavior, or permission/auth needs.

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 compact sentences with the core scope front-loaded; nothing is wasteful. The second sentence, 'Scores and adjusted amounts describe the comparable model,' is slightly vague about what the model actually is.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple read-only lookup this is mostly adequate, but with no output schema the description should say more about what a comparable record contains and whether paginated results are bounded. It covers the purpose and hints at fields but leaves the return shape underspecified.

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%, so all three parameters (id, limit, offset) are already documented, including accepted ID formats and bounds. The description adds no ID-format, pagination, or 'verified' semantics beyond what the schema states, 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: read the published comparable sale set for a verified NYC property or condo unit. The domain and record type distinguish it reasonably well from siblings like list_nyc_recorded_sales or search_nyc_properties, though it never names an alternative explicitly.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance and no alternatives named. The phrase 'verified NYC property' hints at a prerequisite (an already-resolved property ID) but this is left implicit, so an agent must infer routing from the sibling names alone.

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.