Dojazdomat

rank_for_two

Read-onlyIdempotent

Rank Warsaw neighborhoods for two people who work in two places (para, dwa biura): median rent, both commutes and monthly_cost (rent + both commutes valued at the minimum wage). Each person can use a different mode. Neighborhoods with fewer than 20 ads are skipped.

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": {
      "a_lat": "<a_lat>",
      "a_lon": "<a_lon>",
      "b_lat": "<b_lat>",
      "b_lon": "<b_lon>"
    },
    "name": "rank_for_two"
  }
}

Input Schema

Name	Required	Description	Default
`sort`	No	best = rent + both commutes valued at the minimum wage (default); fair = shortest longer commute first; rent = cheapest first	best
`a_lat`	Yes	Latitude, WGS84, 51.98-52.48 (Warszawa and commuter belt)
`a_lon`	Yes	Longitude, WGS84, 20.62-21.48 (Warszawa and commuter belt)
`b_lat`	Yes	Latitude, WGS84, 51.98-52.48 (Warszawa and commuter belt)
`b_lon`	Yes	Longitude, WGS84, 20.62-21.48 (Warszawa and commuter belt)
`limit`	No
`rooms`	No	Rooms 1-4 (4 = 4+); omit for any / liczba pokoi
`mode_a`	No	transit (default, weekday morning public transport + walking), bike, walk or car (rush hour) / komunikacja, rower, pieszo, auto	transit
`mode_b`	No	transit (default, weekday morning public transport + walking), bike, walk or car (rush hour) / komunikacja, rower, pieszo, auto	transit
`max_rent`	No	Max neighborhood median rent, PLN/month
`max_commute_min`	No	Max commute minutes for each person

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 8, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, so the description only needs to add ranking semantics — which it does: the cost model, the minimum-wage commute valuation, per-person mode choice, and the 20-ad minimum sample that silently drops neighborhoods. No return shape or data-recency information is given, though an output schema exists.

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 tight sentences, front-loaded with the purpose, then the ranking inputs, then the skip rule. The Polish parenthetical (para, dwa biura) is mildly extraneous for an English-reading agent but does no harm and is small relative to the useful content.

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?

For an 11-parameter tool with full annotations and an output schema, the description supplies the non-obvious parts: what is being optimized, how commute is monetized, and the sample-size cutoff. It leaves the sort variants and rent/commute caps entirely to the schema, which is acceptable given high coverage, but does not mention the default limit or data source.

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?

Adds meaning beyond the 91%-covered schema: it defines monthly_cost as rent plus both commutes valued at the minimum wage, clarifies that each person may use a different mode (mode_a vs mode_b independence), and discloses the implicit <20-ads filter that no schema field exposes. It does not cover limit or the max_rent/max_commute_min filters, but the schema already describes those.

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 verb (rank) plus resource (Warsaw neighborhoods) and a precise scope: two people working in two different places. The dual-origin framing distinguishes it from the single-origin rank_neighborhoods and from compare_neighborhoods without needing to name them.

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 two-person framing implies when this tool applies rather than stating it explicitly. No sentence tells the agent to prefer this over rank_neighborhoods (one origin) or compare_neighborhoods (pairwise comparison), and no exclusions are given; usage must be inferred from the scope description.

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?