MCP server for inspecting, querying, and extracting features from PMTiles archives
Five tools with clear verb-noun naming (inspect_, list_, get_, query_, search_). All have descriptions (avg 85 chars) and input schemas with type definitions. Tool annotations (readOnlyHint) present. However, output schemas missing for 2/5 tools (get_tile, query_location), parameter descriptions lack constraint details (e.g., zoom 0-22 stated but not in schema), and error handling is basic. No pagination support despite search_bbox accepting maxTiles. Schemas use Zod but not all constraints are visible in the JSON Schema shape exported.
Fetch a PMTiles tile as GeoJSON features or raster image content
Inspect a PMTiles archive: metadata, bounds, zoom range, layers, format
List vector layers and attribute schemas from a PMTiles archive
Query features or raster tiles at a latitude/longitude location
Search vector features intersecting a bounding box in a PMTiles archive
Output schemas missing for 2/5 tools (get_tile, query_location). LLMs cannot plan downstream operations without knowing return structure.
Parameter constraints (zoom 0-22, lat/lon bounds, bbox format) documented in descriptions but not enforced in JSON Schema. Zod validation exists in code but not visible in exported schemas.
search_bbox accepts maxTiles parameter but no pagination cursor or offset. Large result sets could exhaust context window without limit enforcement in response.
Error handling returns JSON-stringified ToolError objects but lacks recovery guidance. E.g., 'TILE_NOT_FOUND' does not suggest alternative zoom levels or nearby tiles.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 69 | 2025-06-18+ | v2 |
URL parameter accepts any http(s) URL but no validation against private IP ranges documented in code (PMTILES_MCP_ALLOW_PRIVATE env var exists but not mentioned in tool descriptions).