Skip to main content
Glama

Realtors Dashboard

Search published NYC properties and condo units

search_nyc_properties
Read-onlyIdempotent

Browse verified property or residential condo unit identities. Filter by exact NYC ZIP or an address fragment. Property prices are labeled separately from condo sales.

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

Input Schema

NameRequiredDescriptionDefault
qNoAddress fragment
zipNoFive-digit ZIP code, including leading zeroes
kindNoRecord type (default property)
limitNoMaximum records to return
offsetNoNumber of records to skip

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/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 behavior, so the safety profile is covered. The description adds that records are 'verified' and that property prices and condo sales prices are distinguished, which is genuine domain context, but it says nothing about result ordering, pagination behavior, or what happens when filters match nothing.

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?

Three short sentences, front-loaded with the resource and the two filter modes; nothing is redundant with the annotations. The closing sentence on price labeling is slightly tangential to search invocation but does carry data meaning.

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?

With no output schema, no required parameters, and five optional params, the definition should hint at what a returned 'property identity' record contains and how limit/offset paginate or order results; it does neither. Annotations and full schema coverage carry most of the remaining burden, so this is adequate but not complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning: ZIP matching is exact while q is a fragment/partial match — a distinction the schema's 'Address fragment' wording does not settle. It also implies kind selects between property and condo unit, matching the price-labeling note.

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: browse verified NYC property or condo unit identities, with filtering by ZIP or address fragment. This distinguishes it from single-record siblings like get_nyc_property, 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 Guidelines3/5

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

Usage is implied (a browse/search entry point for NYC records) but there is no explicit when-to-use or when-not-to-use guidance, and no routing to search_florida_recorded_sales, get_nyc_property, or the market-aggregate siblings. The note about prices being labeled separately from condo sales is a data caveat rather than invocation guidance.

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.