Crawlora MCP

wolt_cities

Read-only

Wolt's directory of every city it operates in, each with the coordinate pair the other wolt_* tools take, plus slug, country codes, and timezone. Optionally filter by country or sort nearest-first from a reference coordinate.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "wolt_cities"
  }
}

Input Schema

Name	Required	Description
`country`	No	Optional ISO 3166-1 country code to restrict the directory to, either alpha-2 (FI) or alpha-3 (FIN), case-insensitive. Wolt's own endpoint has no country parameter, so this is applied to the returned directory.
`latitude`	No	Optional reference latitude. When both coordinates are given, every city carries its distance from them and the list is returned nearest-first.
`longitude`	No	Optional reference longitude. Must be given together with latitude.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 5, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and scope are covered. The description adds useful behavioural detail by listing what each record contains and that the set is the full worldwide directory. It does not disclose pagination or result-count behavior, so it goes slightly beyond baseline but not richly.

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 tightly packed sentences with zero filler. The resource scope and payload lead, and the optional filter/sort behavior follows, so the most important information is front-loaded.

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-value detail is not required, and the description covers the directory contents, the optional country filter and the coordinate-based sort. It is essentially complete for a read-only directory tool, missing only minor operational notes like result volume or freshness.

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 three parameters are already documented, including the alpha-2/alpha-3 acceptance and the 'must be given together' constraint on longitude. The description only restates the country filter and nearest-first ordering, adding no syntax or edge-case detail 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 resource ('Wolt's directory of every city it operates in') and enumerates the payload (coordinate pair, slug, country codes, timezone). Crucially, it distinguishes itself from siblings by noting the coordinate pair is what 'the other wolt_* tools take', so an agent understands this is the location lookup layer, not a restaurant search.

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?

It gives clear context (fetch the city list / coordinates that other wolt_* tools consume) and describes the two optional behaviors, filtering by country and nearest-first sorting from a reference point. It stops short of naming an alternative tool or stating when NOT to use it, but the routing intent is clear.

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

All Crawlora MCP 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?