Search events and places for the signed-in user.
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | Natural-language query. | |
| user_lat | No | Decimal degrees. Send a number, not a string. | |
| user_lng | No | Decimal degrees. Send a number, not a string. | |
| radius_km | No | Radius in kilometers. Send a number, not a string. | |
| max_results | No | max_results | |
| selected_type | No | selected_type | |
| selected_genres | No | selected_genres | |
| selected_subcategories | No | selected_subcategories |
Changes observed during successful MCP inspections.
Input schema / propertiesAdded value: +{
+ "max_results": {
+ "description": "max_results",
+ "type": "integer"
+ },
+ "query": {
+ "description": "Natural-language query.",
+ "type": "string"
+ },
+ "radius_km": {
+ "description": "Radius in kilometers. Send a number, not a string.",
+ "type": "number"
+ },
+ "selected_genres": {
+ "description": "selected_genres",
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ },
+ "selected_subcategories": {
+ "description": "selected_subcategories",
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ },
+ "selected_type": {
+ "description": "selected_type",
+ "type": "string"
+ },
+ "user_lat": {
+ "description": "Decimal degrees. Send a number, not a string.",
+ "type": "number"
+ },
+ "user_lng": {
+ "description": "Decimal degrees. Send a number, not a string.",
+ "type": "number"
+ }
+}Input schema / requiredAdded value: +[
+ "query"
+]Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden. It discloses only that results are scoped to the signed-in user and cover events and places; it does not state that this is a read-only operation, describe result format or pagination, or mention any auth, rate, or personalization behavior.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single front-loaded sentence with no wasted words. It is appropriately concise, though it is very minimal for an 8-parameter search tool, which borders on under-specification rather than conciseness.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a search tool with 8 parameters, no annotations, no output schema, and many sibling search tools, the description is incomplete. It omits return-value expectations, result behavior, parameter guidance, and sibling differentiation, leaving significant gaps for correct invocation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the baseline is 3 even though the description adds no parameter meaning. Several schema descriptions are placeholder-like (e.g., 'max_results', 'selected_type'), but the description does not compensate or add syntax or format details beyond the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb (Search) and resources (events and places), and it scopes results to the signed-in user. It does not, however, distinguish the tool from the many sibling search_* tools such as search_embed, search_query_router, or search_rerank, so sibling differentiation is absent.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no guidance on when to use this tool versus alternatives. With many sibling search and retrieval tools available, the description gives no conditions, exclusions, or routing advice to help an agent choose correctly.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.