OpenVan MCP Server

Get Event Details

get_event

Read-onlyIdempotent

Retrieve full details for a single vanlife event using its slug. Returns localized information and an interactive card in the user's chosen language for trip planning.

Instructions

Get full details for a single vanlife event by its slug.

Input Schema

Name	Required	Description	Default
`slug`	Yes	Event slug, e.g. caravan-salon-duesseldorf-2026.
`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

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

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

Changed2 schema fields changedv0.6.4Oct 15, 2026

addedInput schema / properties / locale / description

Added 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, destructiveHint=false, and openWorldHint, so the safety profile is covered. The description adds domain scope ('vanlife event') and detail level ('full details'), but does not add extra behavioral context such as error handling for invalid slugs.

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 a single, front-loaded sentence with no wasted words. It efficiently communicates the core operation.

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?

The output schema exists and annotations are rich, so the description need not explain return values or safety. It is mostly complete for this simple lookup, though it could better distinguish from list_events.

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 100%, so both slug and locale are fully documented in the schema. The description mentions slug but adds no meaning beyond the schema for locale or slug format.

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 description states a specific verb and resource: retrieving full details for a single vanlife event by slug. It is clear and specific, though it does not explicitly distinguish this tool from the sibling list_events.

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 phrase 'single ... event by its slug' implies usage when a slug is known and detail is needed, but it gives no explicit when/when-not guidance or mention of list_events as an alternative.

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