OpenVan MCP Server

List Vanlife Events

list_events

Read-onlyIdempotent

List vanlife expos, festivals, meetups, forums, and road trips, and filter them by status, type, country, or free-text search to find relevant events.

Instructions

List vanlife events: expos (Caravan Salon), festivals, meetups, forums, road trips. Filter by status, type, country, or free-text search.

Input Schema

Name	Required	Description	Default
`type`	No	Event type filter.
`limit`	No
`locale`	No	Language the user writes in (en, ru, de, fr, es, pt, tr). Set it on every call: the answer and the interactive card are shown in this language and units; without it the card falls back to the app's interface language.	en
`search`	No	Free-text search in event name.
`status`	No	Event time status.	upcoming
`country`	No	ISO 3166-1 alpha-2 country code.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv0.9.7Oct 25, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```
- removedInput schema / properties / limit / default
```
Removed value: -15
```
- changedOutput schema / additionalProperties
```
Previous value: -trueNew value: +{}
```

Changed2 schema fields changedv0.6.4Oct 15, 2026

changedInput schema / properties / locale / description

Previous value: -"Language for localized fields."New value: +"Language the user writes in (en, ru, de, fr, es, pt, tr). Set it on every call: the answer and the interactive card are shown in this language and units; without it the card falls back to the app's interface language."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": true,
+  "properties": {},
+  "type": "object"
+}

First observedv0.6.0Oct 3, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered by structured data. The description adds domain examples (Caravan Salon) but no behavioral context such as the default status filter, pagination/limit behavior, or that results reflect a live open-world dataset. Adequate but thin given annotations carry most of the load.

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?

Two tight sentences with no waste, and the resource scope is front-loaded before the filter list. Every clause earns its place.

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?

An output schema exists and the input schema is well documented, so the description needn't explain return values. The main residual gap is the absence of a pointer to get_event and the default-status behavior, which would help an agent call it correctly on the first try.

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 description coverage is 83%, so the schema already documents type, status, country, search and even the locale default behavior. The description merely restates the filter names without adding syntax, format, or interaction detail, so baseline 3 applies.

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?

Uses a specific verb ('List') and resource ('vanlife events') and enumerates the event categories (expos, festivals, meetups, forums, road trips), which concretely scopes the tool. It does not differentiate from the sibling get_event, which clearly retrieves a single event, so an agent must infer the list-vs-lookup split.

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

Usage Guidelines3/5

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

The second sentence names the available filters, which implies usage, but there is no explicit when-to-use guidance and no mention of the alternative get_event for fetching a single event. Nothing says the default status is 'upcoming', so an agent could misread results as all-time.

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