Skip to main content
Glama

rent_stats

Read-onlyIdempotent

Asking-rent statistics (n, median, p25, p75) of rental ads within radius_m of a point (statystyki cen najmu w promieniu). Aggregates only; if fewer than 20 ads match, the result is suppressed (widen radius or relax filters). Radius is snapped to a fixed step (see radius_m) so queries cannot be differenced to single ads.

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": {
      "lat": "<lat>",
      "lon": "<lon>"
    },
    "name": "rent_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
latYesLatitude, WGS84, 51.98-52.48 (Warszawa and commuter belt)
lonYesLongitude, WGS84, 20.62-21.48 (Warszawa and commuter belt)
roomsNoRooms 1-4 (4 = 4+); omit for any / liczba pokoi
measureNo'total' PLN/month or 'per_m2' PLN/m2/monthtotal
max_areaNoMax area m2
min_areaNoMin area m2
radius_mNoRadius in metres, 200-5000; snapped to the nearest of 300, 500, 750, 1000, 1500, 2000, 3000, 5000 (the answer states the radius used)

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / radius_m / description
      Previous value: -"Radius in metres, 200-5000"New value: +"Radius in metres, 200-5000; snapped to the nearest of 300, 500, 750, 1000, 1500, 2000, 3000, 5000 (the answer states the radius used)"
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile needs no restating. The description adds two non-obvious behaviors not in annotations: k-anonymity suppression below 20 ads and radius snapping to discretized steps specifically to prevent differencing attacks — meaningful operational and privacy context.

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 sentences, front-loaded with the aggregation scope before the caveats, and each sentence carries real information. Minor redundancy: the radius-snapping statement duplicates what radius_m's schema description already says.

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?

With an output schema present, return values need no explanation, and the description covers the two things an agent would otherwise get wrong: suppression and radius quantization. It is slightly thin on the data's temporal scope (how recent the ads are) and on any cost/latency expectations, but nothing critical for correct invocation is missing.

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%, so all seven parameters, the measure enum, and the radius snapping grid are already documented in structured fields; baseline 3 applies. The description largely restates the snapping rule rather than adding new meaning such as interaction between area filters and the suppression threshold.

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: aggregates asking-rent statistics (n, median, p25, p75) of rental ads within a radius of a point, including the output measures. It is not confused with rent_trend or compare_neighborhoods, but it never names those siblings to sharpen the distinction.

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 description gives failure-mode guidance ('if fewer than 20 ads match... widen radius or relax filters'), which is genuinely actionable. However, it never says when to choose this over rent_trend (temporal) or compare_neighborhoods/rank_neighborhoods (multi-area ranking), so the routing decision is left to inference.

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.

Resources