MCP filtering, sorting and proximity

Both find_venues and search_venues support the structured filters below. Use find_venues for category/type discovery under a resolved place and search_venues when you have a concrete keyword such as “ramen” or “rooftop bar”.

Filter	Meaning
`category`	Exact case-sensitive category (such as `Italian`, `Museum`, `Cocktail Bar`)
`location_type`	Finer exact venue classification (`Pub`, `Cafe`, `Museum`, etc.)
`price_level`	`inexpensive`, `moderate`, `expensive`, `very_expensive`
`min_rating`	Review-rating minimum on the 0–5 scale
`min_reviews`	Minimum number of review votes
`environment`	`Indoor`, `Outdoor`, `Indoor and Outdoor`
`ambience`, `audience`, `amenities`	Structured tag arrays, AND match
`experience`, `sustainability`, `weather_suitability`, `access`	Structured tag arrays, AND match
`style_visual`, `style_social_media`, `style_architecture`, `style_aesthetic`	Structured tag arrays, AND match
`near`	Coordinates with optional radius; 0.1–50 km, default 5 km
`min_place_score`	Minimum Place Score, 0–100. Most venues score 20–50; 70+ is excellent; 90+ is a city's very best

Array values are enumerated in the tool-specific schema reference, including exact case and punctuation. Multiple values in an array mean every specified tag must be present.

Ordering

MCP `sort_by`	Result
`best`	Evendo ranking, or nearest-first when `near` is set
`rating`	Highest review average first; consider `min_reviews`
`reviews`	Most reviewed first
`nearest`, `farthest`	Distance-based; require `near`
`place_score`	Highest Evendo Place Score first

Missing sort values are placed last according to the tool schema. Do not equate best with Place Score unless the service explicitly documents that behavior; use the score sort explicitly for score-ranked results.

Geographical proximity

json

{
  "place_id":"27799",
  "venue_type":"Restaurants",
  "near":{"lat":40.41378,"lon":-3.69213,"radius_km":2},
  "sort_by":"nearest",
  "limit":10
}

For “near the Prado Museum”, first look up that landmark/attraction and use its returned coordinates in near; do not invent coordinates.

Pages

Both venue discovery tools support limit from 1–50 (default 10) and an opaque cursor. Do not reuse a cursor after changing any filter or sort setting. See Responses and pagination.