Skip to main content
Glama

Côte Privée: private driver in Burgundy

Find events and wine festivals

find_events
Read-onlyIdempotent

Wine fairs, festivals, auctions and cultural events between two dates, at their next appearance: id (event:, which quote takes as to), placeId, dates and whether they are confirmed, website, and a driver quote for the day asked within the event (dated once confirmed): a wine day for a wine event in a wine village, else the ride from Beaune (or origin) and back later the same day.

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": "find_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoDefault a year after from.
fromNoDefault today.
langNoar: Arabic notes, data in English.
limitNo
queryNoWords, e.g. "Hospices", "jazz".
originNoStart of the driver quote (default beaune).

Output Schema

NameRequiredDescriptionDefault
toYes
fromYes
countYes
eventsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedOutput schema / properties / events / items / properties / driverQuote / properties / deposit / deprecated
      Added value: +true
    • addedOutput schema / properties / events / items / properties / driverQuote / properties / payment
      Added value: +{
      +  "enum": [
      +    "in full when the driver confirms"
      +  ],
      +  "type": "string"
      +}
    • changedOutput schema / properties / events / items / properties / driverQuote / required
      Previous value: -[
      -  "service",
      -  "title",
      -  "price",
      -  "deposit",
      -  "bookUrl"
      -]New value: +[
      +  "service",
      +  "title",
      +  "price",
      +  "payment",
      +  "deposit",
      +  "bookUrl"
      +]
  2. Changed1 schema field changed
    • changedInput schema / properties / origin / enum
      Previous value: -[
      -  "beaune",
      -  "dijon",
      -  "lyon",
      -  "paris",
      -  "geneva",
      -  "creusot",
      -  "lfsd",
      -  "lfgj",
      -  "lfgf",
      -  "lfgz",
      -  "lflh",
      -  "lfgi",
      -  "lfep"
      -]New value: +[
      +  "beaune",
      +  "dijon",
      +  "lyon",
      +  "paris",
      +  "geneva",
      +  "creusot",
      +  "lfsd",
      +  "lfgj",
      +  "lfgf",
      +  "lfgz",
      +  "lflh",
      +  "lfgi",
      +  "lfep",
      +  "macon",
      +  "chalon",
      +  "reims",
      +  "epernay",
      +  "troyes",
      +  "colmar",
      +  "strasbourg",
      +  "besancon",
      +  "arbois",
      +  "annecy",
      +  "chamonix",
      +  "avignon"
      +]
  3. First observed

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds genuinely useful behavior: results reflect an event's "next appearance" and the attached driver quote is only dated once the event is confirmed, i.e. some returned data is provisional. It does not mention result limits or what happens with no matches, leaving some gaps.

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

Conciseness2/5

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

It is a single sprawling sentence with nested parentheticals and awkward constructions such as "a driver quote for the day asked within the event" and "else the ride from Beaune (or origin) and back later the same day." The purpose is buried under return-value detail, so the description is not front-loaded or scannable.

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

Completeness3/5

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

With an output schema present and four annotations, the description only needs to cover intent, scope and non-obvious behavior. It covers event scope, date range, origin and provisional-quote behavior, but says nothing about limit, query semantics, or when to prefer this over plan_wine_day/quote, leaving it merely adequate for a 6-parameter discovery tool.

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 largely documents from/to defaults, lang, limit, query and the origin enum. The description reinforces the date-range and origin semantics ("between two dates", "from Beaune (or origin)") but adds nothing about query matching or limit behavior. Baseline 3 is appropriate given the schema does the heavy lifting.

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 opening names a specific verb and resource set: wine fairs, festivals, auctions and cultural events within a date range. It also enumerates the fields returned (id, placeId, dates, confirmation status, website, driver quote), so an agent knows what it gets. The phrasing is convoluted ("which quote takes as to", "the day asked within the event"), which blurs the edges but does not obscure the core purpose.

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?

There is no explicit when-to-use guidance and no routing against siblings like plan_wine_day, quote, or search_places. The only relationship hint is the parenthetical that quote consumes the returned id, which is a data-flow note rather than a selection rule. An agent must infer from the name alone when this tool beats its siblings.

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.

Resources