ROOTE MCP
Errors & Limits
ROOTE MCP validation, upstream errors, and operational limits.
Page actions
ROOTE MCP validates every tools/call against the schema returned by tools/list. Tool errors remain MCP results marked as errors; preserve the reported code, message, metadata, and Retry-After information instead of inventing a successful answer.
| Tool | Key schema limits |
|---|---|
geocode | q 1–200; language 1–35; country two letters |
place_search | q 1–200; valid lat and lon together |
reverse_geocode | Required valid lat and lon; language 1–35 |
nearby | Radius maximum 400 m; limit maximum 100 |
mobility_nearby | Radius maximum 400 m; limit maximum 100 |
transit_nearby | Radius maximum 5,000 m; limit maximum 200 |
services_nearby | Radius maximum 1,500 m; limit maximum 200 |
REST and MCP schemas are separate contracts. Do not pass REST-only parameters to a tool.
The anonymous MCP path inherits the API Free projection and RATE_LIMITED response. MCP does not maintain a second credit balance or business quota. Invalid and revoked Bearers remain authentication failures with no anonymous fallback.