Dojazdomat

reachable_neighborhoods

Read-onlyIdempotent

Every neighborhood from which this point (e.g. the office) is reached within max_minutes, fastest first (zasieg w N minut). Lists also neighborhoods with too few ads for a price (median_rent null), unlike rank_neighborhoods.

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": "reachable_neighborhoods"
  }
}

Input Schema

Name	Required	Description	Default
`lat`	Yes	Latitude, WGS84, 51.98-52.48 (Warszawa and commuter belt)
`lon`	Yes	Longitude, WGS84, 20.62-21.48 (Warszawa and commuter belt)
`mode`	No	transit (default, weekday morning public transport + walking), bike, walk or car (rush hour) / komunikacja, rower, pieszo, auto	transit
`limit`	No
`rooms`	No	Rooms 1-4 (4 = 4+); omit for any / liczba pokoi
`max_minutes`	No	Max minutes from home to this point

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 cover the read-only, idempotent, closed-world profile. The description adds two things they don't: the result ordering (fastest first) and the fact that rows may carry a null median_rent rather than being dropped — a genuinely important behavioral nuance for interpreting output. It doesn't discuss limits/truncation behavior, keeping it short of a 5.

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 tight sentences, with the core behavior and sort order front-loaded and the sibling comparison placed after. The Polish parenthetical is short and useful for query matching rather than filler.

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 six parameters but only two required, plus a 83%-documented schema and an output schema present, the main things an agent needs are covered: what is listed, how it is ordered, and the null-median edge case. Only the 'limit' parameter and truncation behavior are left unexplained.

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 83%, so lat/lon/mode/rooms/max_minutes are already documented in the schema; only 'limit' lacks a description. The prose reinforces that max_minutes is measured from home to this point but adds no syntax or default information beyond the schema, so baseline 3 applies.

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?

States a specific operation: list every neighborhood from which the given point is reachable within max_minutes, ordered fastest first. It also names the sibling it differs from (rank_neighborhoods), so an agent can distinguish the two 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The second sentence gives an explicit selection criterion against rank_neighborhoods: this tool also returns neighborhoods with too few ads for a price (median_rent null). That is a clear 'use this instead when...' signal, though it doesn't state when rank_neighborhoods would be preferable or any prerequisites.

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?