Skip to main content
Glama

Realtors Dashboard

Get a published NYC property or condo unit

get_nyc_property
Read-onlyIdempotent

Resolve a verified published NYC property ID, condo unit BBL, or condo unit page slug.

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

Input Schema

NameRequiredDescriptionDefault
idYesExact published property ID, condo unit BBL, or condo unit slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/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 the meaningful constraint that only verified, published properties resolve, hinting at failure for unpublished records. It does not say what a successful resolution returns or how misses are surfaced.

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 with no filler, and the accepted identifier types are front-loaded for immediate scanning. Nothing can be trimmed without losing the enumerated identifier kinds.

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 one-parameter read-only lookup this is close to adequate, and annotations plus a fully described schema carry most of the burden. However, with no output schema, the description leaves the agent guessing what a resolved property object contains and what happens on a non-match.

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 description coverage is 100% and the single 'id' parameter is documented in the schema, so the baseline of 3 applies. The description earns a small bump by restating the three mutually exclusive identifier families in the same terms as the schema, confirming the polymorphism of the one field.

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?

The description gives a specific verb ('Resolve') plus the exact resource ('published NYC property ID, condo unit BBL, or condo unit page slug'), so an agent knows precisely what input forms are accepted. It stops short of naming or contrasting siblings such as search_nyc_properties, so the token-based lookup versus search distinction is only implied.

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 rather than stated: the emphasis on 'Exact' identifiers and 'verified published' records signals this is the path to take when you already hold a canonical ID, BBL, or slug. There is no explicit when-not guidance and no sibling alternative named for the fuzzy-search case.

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.