MCP tools return structured JSON, not free text. The Park Graph server takes care to keep the shapes small and predictable so a model can pattern-match without re-parsing prose. search_lots answers with the lots, nearest first, and a short top-level summary line the model can quote when the user just wants a one-line answer.
search_lots result with an API key (truncated)json
{
"lots": [
{ "id": "5c2f7d1e-…", "name": "Vail Village Lifthouse Lot", "distance_km": 0.3, "availability": { "available_spaces": 12 }, "pricing": { "base_rate": 8.0, "rate_unit": "hour" } },
{ "id": "7c4e1f02-…", "name": "Lionshead Public Parking", "distance_km": 1.6, "availability": { "available_spaces": 87 }, "pricing": { "base_rate": 6.0, "rate_unit": "hour" } }
],
"summary": "2 lots within 5 km. Top: Vail Village Lifthouse Lot (0.3 km, $8/hr, 12 left); Lionshead Public Parking (1.6 km, $6/hr, 87 left)."
}
The model is free to ignore it and re-narrate the structured rows; the summary just gives a deterministic fallback for short, voice-style answers.