Skip to main content
Glama

Realtors Dashboard

NYC Price per Square Foot Benchmark

compare_nyc_price_per_square_foot
Read-onlyIdempotent

Calculate a property's price per square foot and compare it with its exact NYC ZIP's recorded-sale median.

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>",
      "price": "<price>",
      "squareFeet": "<squareFeet>"
    },
    "name": "compare_nyc_price_per_square_foot"
  }
}

Input Schema

NameRequiredDescriptionDefault
zipYesFive-digit NYC ZIP code
priceYesProperty price in US dollars
squareFeetYesInterior area in square feet

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 this a read-only, idempotent, closed-world operation, so the safety profile is covered. The description adds genuine context by specifying the benchmark is the 'recorded-sale median' for the exact ZIP, but it does not say what happens when a ZIP has no recorded sales or whether the comparison is a ratio, percentile, or delta.

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 that front-loads the calculation and then the comparison, with no redundant restatement of the tool name or schema fields. Every clause carries information.

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 carries the burden of explaining the return shape, and it only vaguely says results are 'compared' without indicating whether the agent receives a median value, a ratio, or a qualitative verdict. Given a three-parameter, single-purpose tool, this is adequate but leaves a real gap in what to expect back.

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. The description earns an extra point by stressing 'exact NYC ZIP', signaling that the benchmark is matched on the precise ZIP code with no fallback to county or city-wide medians, which constrains how the zip argument should be chosen.

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 names two specific actions (compute price per square foot, compare to a benchmark) and a precise resource (the exact NYC ZIP's recorded-sale median). This clearly distinguishes it from a ZIP-level market snapshot or momentum tool, though it never names or rules out 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 only implied: an agent can infer the tool is for evaluating a single property against its local ZIP benchmark. There is no statement of when to prefer it over the sibling ZIP snapshot tool, and no preconditions such as requiring recorded sales in that ZIP.

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.