Dojazdomat

rank_neighborhoods

Rank Warsaw neighborhoods for a workplace: median rent, commute minutes, value score (rent vs typical rent in the same commute band, like the map), monthly_cost (rent + commute valued at the minimum wage) and Pareto flag (no neighborhood both faster and cheaper) (ranking osiedli: czynsz, dojazd, wartosc, front Pareto). Same data and rules as the map: neighborhoods with fewer than 20 ads are skipped. Sorted by best (rent + commute cost, the map's order) unless sort is given.

Input Schema

Name	Required	Description	Default
`sort`	No	best = rent + commute valued at the minimum wage (default, the map's order, total measure only); value = score vs typical rent in the same commute band; commute = fastest first; rent = cheapest first	best
`limit`	No
`rooms`	No	Rooms 1-4 (4 = 4+); omit for any / liczba pokoi
`measure`	No	'total' PLN/month or 'per_m2' PLN/m2/month	total
`max_rent`	No	Max neighborhood median rent (PLN, or PLN/m2 if measure=per_m2)
`office_lat`	Yes	Latitude, WGS84, 51.98-52.48 (Warszawa and commuter belt)
`office_lon`	Yes	Longitude, WGS84, 20.62-21.48 (Warszawa and commuter belt)
`max_commute_min`	No	Max commute minutes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 24, 2026

addedInput schema / properties / sort

Added value: +{
+  "default": "best",
+  "description": "best = rent + commute valued at the minimum wage (default, the map's order, total measure only); value = score vs typical rent in the same commute band; commute = fastest first; rent = cheapest first",
+  "enum": [
+    "value",
+    "best",
+    "commute",
+    "rent"
+  ],
+  "title": "Sort",
+  "type": "string"
+}

First observedOct 21, 2026

TDQS

A3.7/5.0

Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does a good job: it discloses that neighborhoods with fewer than 20 ads are skipped, explains the default sort, and defines the value and Pareto metrics. It is still somewhat vague about the upstream data and rule source by saying 'same data and rules as the map'.

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?

The description is front-loaded with the purpose and then supplies the key rules and metrics. It is somewhat dense and includes parenthetical Polish aliases that add clutter, but the content generally earns its place.

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?

Given the moderate complexity, high schema coverage, and an output schema, the description is mostly complete. It covers the exclusion rule and default ordering, though it could better explain how this tool relates to the narrower sibling tools.

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 88%, so the schema already documents nearly all parameters. The description reinforces the default sort behavior but adds little parameter-level meaning beyond the schema.

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 clearly states a specific verb and resource: ranking Warsaw neighborhoods for a workplace. It distinguishes the result set through its combined rent/commute/value/Pareto criteria, but it does not explicitly contrast the tool with siblings such as rent_stats or commute_time.

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 use case is implied by 'for a workplace' and the ranking context, but there is no explicit guidance on when to choose this tool over rent_stats or commute_time. It also does not state exclusions beyond the 20-ad threshold.

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?