Skip to main content
Glama

Viventii Events, Leisure, POIs, Tickets & Ticket Resale

Search Places, POIs & Sights

search_places_and_pois
Read-onlyIdempotent

Searches permanent places and Points of Interest (POIs) on Viventii: attractions, museums, parks, zoos, cinemas, theaters, clubs, bars, restaurants, and shops.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_places_and_pois"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNoCity name (e.g. "Berlin", "Köln", "Bonn", "München")
limitNoMax places to return (default 20, max 50)
queryNoOptional place, sight, or venue name/keyword
localeNoPreferred language code (default: de)
districtNoOptional district or quarter
latitudeNo
poiTypesNoOptional POI types (museum, park, landmark, castle, zoo, aquarium, cinema, theater, swimming_pool, climbing_gym)
radiusKmNo
longitudeNo
categoriesNoOptional categories (Art, Outdoors, Family, Sports, Cinema, Theater, Music, Food, Shopping)
venueTypesNo
cuisineTypesNo
wheelchairOnlyNoFilter for wheelchair-accessible places

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered; the description's only added behavioral context is that the data lives in Viventii's own catalog. It says nothing about ranking, how latitude/longitude/radiusKm interact for geo search, whether filters are AND-combined, or what a broad unfiltered call returns, which matters for a 13-parameter search tool.

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

Conciseness4/5

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

A single front-loaded sentence with verb, resource, and a scannable entity list; nothing is redundant. It is arguably over-indexed on the entity list at the expense of usage or behavioral detail, but no wording is wasted.

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

Completeness2/5

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

Thirteen optional parameters, no output schema, and only 62% schema description coverage mean the description should carry more. It omits how the geographic filters behave, how filter arrays combine, what the response contains, and when to prefer this over event/discovery siblings, leaving significant gaps for a tool of this complexity.

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

Parameters3/5

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

Schema coverage is 62%, above the low-coverage threshold but with real gaps: latitude, longitude, radiusKm, venueTypes and cuisineTypes carry no schema descriptions, and the tool description supplies no meaning for any of them. The entity enumeration loosely maps to poiTypes/categories but adds no syntax, defaults, or combination rules beyond the schema.

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?

States a specific verb ('searches') and a specific resource ('permanent places and Points of Interest'), then enumerates entity classes (attractions, museums, parks, bars, restaurants, shops) so the agent knows exactly what is and isn't in scope. The word 'permanent' implicitly separates it from event-based siblings like search_events, though no sibling is named.

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

Usage Guidelines2/5

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

The description says what is covered but never when to pick this tool over the many siblings (discover_what_to_do, explore_leisure_activities, get_family_and_kids_events). There are no stated prerequisites, exclusions, or alternative routing; the only disambiguation is the incidental contrast between 'permanent' places and events.

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.