Skip to main content
Glama

Realtors Dashboard

NYC ZIP Market Snapshot

get_nyc_zip_market_snapshot
Read-onlyIdempotent

Get sale price quartiles, median price per square foot, sample size, and trend for an exact NYC ZIP.

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": {
      "zip": "<zip>"
    },
    "name": "get_nyc_zip_market_snapshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
zipYesFive-digit NYC ZIP code

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is covered. The description adds value by disclosing the returned payload (including sample size, which signals statistical reliability) in the absence of an output schema. It does not say what happens for a ZIP with insufficient data, whether non-NYC five-digit ZIPs error or return empty, or what time window 'trend' covers.

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?

One sentence, zero filler, with the returned metrics front-loaded so an agent can judge relevance immediately. Nothing is redundant with the parameter schema or annotations.

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?

For a one-parameter, read-only lookup with no output schema, enumerating the returned fields is the most important thing the description can do, and it does that. Minor gaps remain around the trend time window, units, and coverage/insufficiency behavior, but nothing that would prevent a correct call.

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% and the single parameter already carries a description ('Five-digit NYC ZIP code') plus a ^[0-9]{5}$ pattern. The description's only added nuance is 'exact', suggesting no prefix or partial matching. Baseline 3 applies when the schema does the heavy lifting and the description adds only marginal meaning.

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 ('Get') and enumerates exactly which metrics come back: sale price quartiles, median price per square foot, sample size, and trend, scoped to an exact NYC ZIP. A reader knows precisely what data this returns. It stops short of naming or contrasting the sibling tools (list_nyc_market_momentum, compare_nyc_price_per_square_foot), so the differentiation is implicit in the metric set rather than stated.

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?

The word 'exact' implies a single, precise ZIP is required, which hints at when the tool applies versus aggregate or comparison queries. However, there is no explicit when-to-use, no when-not-to-use, and no reference to the sibling tools that serve related questions. Usage is inferable but not spelled out.

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.