Skip to main content
Glama

Evendo Places

Keyword search for venues

search_venues
Read-only

Keyword search over venue names, taglines and descriptions (stemmed; 'brewery' matches 'breweries'; no typo tolerance). Scope it with within_place_id (from resolve_place) — never put the city name in the text. Short, concrete keywords work best: 'ramen', 'rooftop bar', 'flea market'. Combine with filters and/or near.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "text": "<text>"
    },
    "name": "search_venues"
  }
}

Input Schema

NameRequiredDescriptionDefault
nearNoRestrict to this radius around a point; results then sort nearest-first unless sort_by says otherwise. For 'near <landmark>', first find the landmark with search_venues (venue_type Landmarks, then Attractions) and use its location.
textYes1-3 keywords describing what to find.
limitNoResults per page.
accessNoPhysical access difficulty. Every listed value must be present (AND), so pass only what the user actually requires.
cursorNonext_cursor from a previous call with otherwise identical arguments. Never invent one.
sort_byNobest (default): Evendo ranking, or nearest-first when `near` is given. place_score: highest Evendo place score (0-100 overall quality) first. rating: highest average rating first (pair with min_reviews so 1-review places don't win). reviews: most reviewed first ('most popular'). nearest / farthest: by distance, require `near`. Places missing the value sort last. Changing sort_by restarts pagination: don't reuse a cursor from another sort.
ambienceNoAtmosphere tags. Every listed value must be present (AND), so pass only what the user actually requires.
audienceNoWho the place suits / accessibility. Every listed value must be present (AND), so pass only what the user actually requires.
categoryNoExact, case-sensitive category. Restaurants: "Italian", "Japanese", "Mexican", "Indian", "Chinese", "Thai", "French", "Mediterranean", "Seafood", "Steakhouse", "Pizza", "Sushi", "Vegan", "Vegetarian", "Fast Food", "Fine Dining". Bars: "Cocktail Bar", "Wine Bar", "Sports Bar", "Beer Garden". Shopping: "Market", "Boutique", "Mall". Attractions: "Museum", "Park", "Gallery", "Zoo", "Theme Park", "Garden". If unsure of the exact value, use search_venues text instead.
amenitiesNoRequired amenities. Every listed value must be present (AND), so pass only what the user actually requires.
experienceNoExperience tags. Every listed value must be present (AND), so pass only what the user actually requires.
min_ratingNoMinimum average rating, 0-5. "good" = 4.0, "top rated"/"best" = 4.5 (pair with min_reviews).
venue_typeNoRestaurants (incl. cafes, diners), Bars (pubs, nightclubs), Shopping (markets, shops), Attractions (museums, parks, galleries, zoos), Landmarks (monuments, historic sites). Unsure between Attractions and Landmarks? Try both. Omit for vague asks ('spots', 'places').
environmentNo"outdoor"/"terrace"/"al fresco" = Outdoor. For "outdoor seating" make two calls, Outdoor and "Indoor and Outdoor", and merge.
min_reviewsNoMinimum number of reviews; use ~50+ to avoid thinly-rated places. "good" = 10+, "top rated" = 20+.
price_levelNo"cheap"/"budget" = inexpensive; "upscale"/"fancy" = expensive or very_expensive. There is no "free" level; for free places use search_venues with text "free".
country_codeNoISO alpha-2; broad scoping when no place ID is known.
style_visualNoViews. Every listed value must be present (AND), so pass only what the user actually requires.
location_typeNoFiner type than venue_type, exact match, e.g. "Pub", "Cafe", "Restaurant", "Attraction", "Gastropub", "Museum". Pub = Bars + "Pub"; cafe / coffee shop = Restaurants + "Cafe".
sustainabilityNoSustainability tags. Every listed value must be present (AND), so pass only what the user actually requires.
min_place_scoreNoMinimum Evendo place score (0-100 overall quality; most venues are 20-50, 70+ is excellent, 90+ is a city's very best).
style_aestheticNoInterior / design aesthetic. Every listed value must be present (AND), so pass only what the user actually requires.
within_place_idNoRestrict to this place's subtree (city, neighbourhood, region, country).
style_architectureNoArchitecture. Every listed value must be present (AND), so pass only what the user actually requires.
style_social_mediaNoPhoto / social-media appeal. Every listed value must be present (AND), so pass only what the user actually requires.
weather_suitabilityNoWeather suitability. Every listed value must be present (AND), so pass only what the user actually requires.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With readOnlyHint and openWorldHint already covering the safety profile, the description adds useful behavioral detail such as stemming, lack of typo tolerance, and the city-name exclusion. It does not describe result format, pagination, or ranking behavior, though sorting is documented in the schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the core purpose and then layers scoping and keyword guidance without unnecessary wording. Every sentence contributes actionable information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 26-parameter search tool with exhaustive schema descriptions, the description covers the essential invocation path: text, within_place_id scoping, and optional near/filter combination. It does not explain return values or pagination, and there is no output schema to fill that gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description adds meaning for key parameters by explaining that text should contain short concrete keywords and that within_place_id should come from resolve_place rather than embedding a city name.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The first sentence names a specific verb and resource: keyword search over venue names, taglines, and descriptions. It also discloses matching behavior, but it does not explicitly differentiate this tool from sibling search/listing tools such as find_venues or get_venues.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives clear usage constraints: scope with within_place_id from resolve_place, never put the city name in the text, use short concrete keywords, and combine with filters and/or near. It stops short of explicitly naming when to prefer a different search tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.