MCP server for Russian Rosreestr open cadastral data: lookup by cadastral number / address / coordinates, cadastral value with history.
Four tools with complete input schemas and solid descriptions (avg 156 chars, within 10-1024 baseline). All parameters typed and described. Tool names follow verb_noun pattern (lookup_*, get_*). Schemas properly constrained (cadastral_number format, lat/lon bounds, limit ranges). However, output schemas are not explicitly documented in the source, only inferred from response models. Error handling is present but minimal (RosreestrNotFoundError, RosreestrValidationError raised but recovery guidance not visible in tool descriptions). No tool annotations (readOnlyHint, etc.) despite all being read-only. Caching logic is sophisticated but not exposed to the LLM, agent cannot reason about freshness or TTL.
Return the current cadastral value of a Russian property by cadastral number, plus any locally cached revaluation history. Tax base for property tax. Note: full audit trail of historical revaluations is only available via Pro tools or an EGRN extract.
Find Russian cadastral objects matching a free-text address. Searches the public NSPD geoportal index. Returns up to `limit` hits with cadastral numbers and a confidence score.
Get the public characteristics of a Russian cadastral object by cadastral number (formatted XX:XX:XXXXXXX:XXXX, for example 77:01:0001066:1234). Returns area, year built, cadastral cost, permitted use and address. Open data only — no owner PII.
Show Russian cadastral objects (parcels and buildings) at a given geographic point. Coordinates are WGS84 (EPSG:4326). Useful for 'what's at this dot on the map' lookups.
Output schemas not documented in tool descriptions. LLMs cannot plan downstream calls or extract required fields (e.g., cadastral_number from address lookup for chaining to cadastral lookup). Responses are typed Pydantic models but descriptions do not state what fields are returned.
No tool annotations (readOnlyHint, idempotentHint). All four tools are read-only and safe to retry, but this is not declared in the schema. Agents cannot distinguish safe tools from destructive ones without explicit hints.
Error descriptions in tool docstrings do not include recovery guidance. RosreestrValidationError and RosreestrNotFoundError are raised but tool descriptions do not tell the LLM what to do next (e.g., 'If cadastral number format is invalid, try lookup_by_address() with the property address').
Inferred effective spec: 2026-07-28+.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 66 | 2026-07-28+ | v2 |
lookup_by_address and lookup_by_coords accept optional object_types filter but do not document valid enum values. LLMs will hallucinate type names instead of selecting from a constrained set.
lookup_by_address requires minimum 8 characters but description does not state this constraint. Parameter description only says 'Free-text address query' without mentioning the 8-char minimum, forcing LLMs to discover it via trial-and-error.