Skip to main content
Glama

Realtors Dashboard

Get exact NYC recorded-sale aggregates

get_nyc_market_aggregates
Read-onlyIdempotent

Read the active NYC market publication by exact ZIP or published geography ID, including date, sample count, price and trend. State statistics summarize published NYC ZIP benchmarks.

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": {
      "geoType": "<geoType>",
      "geoId": "<geoId>"
    },
    "name": "get_nyc_market_aggregates"
  }
}

Input Schema

NameRequiredDescriptionDefault
geoIdYesZIP, NY, or an exact published geography ID
geoTypeYesPublication geography type

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/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 a closed world, so safety is covered. The description adds that the publication must be 'active' and enumerates returned fields, which is useful context beyond the annotations. The second sentence ('State statistics summarize published NYC ZIP benchmarks') is confusing and arguably works against the multi-geoType schema, since it narrows the reported scope to ZIP benchmarks without explaining what a state or county request returns.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, with the core capability correctly front-loaded. The second sentence is vague and partly redundant, and it introduces ambiguity about geography scope rather than earning its place.

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, the description does list the salient returned fields (date, sample count, price, trend), which is helpful for a two-parameter read tool with full annotation coverage. It omits what happens for unpublished or unknown geography IDs and does not explain the relationship to the ZIP snapshot sibling, leaving real gaps for a tool in a crowded market namespace.

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%, including an enum on geoType and a clear geoId description, so the schema already does the heavy lifting. The description corroborates the geoId semantics ('exact ZIP or published geography ID') but adds no new constraint or format detail. 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 active NYC market publication keyed by exact ZIP or published geography ID. The returned content (date, sample count, price, trend) further pins down what the tool is. It does not, however, distinguish itself from the close sibling get_nyc_zip_market_snapshot, leaving the agent to infer the boundary.

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 explicit when-to-use statement, no mention of prerequisites, and no named alternative among the many market siblings (get_nyc_zip_market_snapshot, get_housing_market, list_nyc_market_momentum). The phrase 'by exact ZIP or published geography ID' implies the input expectation but gives no routing guidance between this tool and near-duplicates.

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.