Dojazdomat

compare_neighborhoods

Read-onlyIdempotent

Compare 2-4 neighborhoods side by side (porownaj osiedla): median rent, p25, p75 and number of ads, plus the commute to an optional workplace. A neighborhood with fewer than 20 matching ads shows suppressed instead of a price.

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": {
      "names": "<names>"
    },
    "name": "compare_neighborhoods"
  }
}

Input Schema

Name	Required	Description	Default
`mode`	No	transit (default, weekday morning public transport + walking), bike, walk or car (rush hour) / komunikacja, rower, pieszo, auto	transit
`names`	Yes	2-4 neighborhood names, e.g. ['Bródno', 'Gocław']
`rooms`	No	Rooms 1-4 (4 = 4+); omit for any / liczba pokoi
`measure`	No	'total' PLN/month or 'per_m2' PLN/m2/month	total
`office_lat`	No	Optional workplace latitude, adds commute_min
`office_lon`	No	Optional workplace longitude

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 8, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare this a safe, idempotent, closed-world read, so the description's job is to add the non-obvious behavior — and it does, disclosing the small-sample suppression rule ("fewer than 20 matching ads shows suppressed instead of a price"). It does not mention error behavior for unrecognized neighborhood names, which is the main remaining gap.

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?

Two sentences with no waste: scope and output metrics come first, the caveat about suppression comes last. The Polish alias is placed inline and costs almost nothing.

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, the description needn't explain return shapes, and it covers the one surprising output case (suppressed values). It is silent on how ambiguous or unknown neighborhood names are resolved, which matters for a name-keyed lookup with a free-text array.

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 tying office_lat/office_lon to a concrete consequence — an added commute column — and by framing the workplace as optional. The 2-4 neighborhood bound restates schema minItems/maxItems and adds little.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource ("Compare 2-4 neighborhoods side by side") and enumerates exactly what is returned: median rent, p25, p75, ad count, and an optional commute. That composite rent-plus-commute scope is what separates it from rent_stats or commute_time without opening either schema.

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 2-4 range and the "optional workplace" phrasing tell the agent when the commute columns appear. There is no explicit when-not guidance and no sibling tool is named as the alternative, so the agent must infer that rank_neighborhoods or rent_stats serve different questions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Dojazdomat tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?