Skip to main content
Glama

Request a charter quote (partner Villiers)

request_charter_quote
Idempotent

Requests confirmed charter prices from partner Villiers for the route of a charter_alternative, for when the user has seen its price range, asked for confirmed prices and given their email. NOT an empty leg: a regular charter; voidjet receives a fee from the partner. voidjet emails the user a link; Villiers receives the request only after the user sends the form on voidjet.io within 48 hours, then emails confirmed options directly. name, phone and message are optional and come from the user.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "origin": "<origin>",
      "destination": "<destination>",
      "departure_date": "<departure_date>",
      "passengers": "<passengers>",
      "email": "<email>"
    },
    "name": "request_charter_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoThe user's name, only if the user gave it.
emailYesThe user's email address.
phoneNoThe user's phone number, only if the user gave it.
localeNoLanguage of texts and links in the result: en or de.en
originYesorigin_code from charter_alternative.
messageNoMessage to the provider in the user's own words, optional.
flexibleNoTrue if the user is flexible on date and time.
passengersYesNumber of passengers travelling.
destinationYesdestination_code from charter_alternative.
departure_dateYesWanted departure date (YYYY-MM-DD).

Output Schema

NameRequiredDescriptionDefault
statusYes
messageYes
expires_atYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • addedInput schema / properties / departure_date / description
      Added value: +"Wanted departure date (YYYY-MM-DD)."
    • addedInput schema / properties / flexible / description
      Added value: +"True if the user is flexible on date and time."
    • addedInput schema / properties / locale / description
      Added value: +"Language of texts and links in the result: en or de."
    • addedInput schema / properties / message / description
      Added value: +"Message to the provider in the user's own words, optional."
    • addedInput schema / properties / name / description
      Added value: +"The user's name, only if the user gave it."
    • addedInput schema / properties / passengers / description
      Added value: +"Number of passengers travelling."
    • addedInput schema / properties / phone / description
      Added value: +"The user's phone number, only if the user gave it."
  2. Added

TDQS

A4.8/5.0
Behavior5/5

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

Goes well beyond the annotations, which only declare a non-read-only, open-world, idempotent, non-destructive call. The description discloses the commercial relationship (voidjet takes a partner fee), the two-stage handoff (voidjet emails a link; Villiers only receives the request after the user submits the form on voidjet.io within 48 hours), and that Villiers then emails options directly — material for telling the user what happens next.

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?

Front-loaded with the core action and the empty-leg exclusion before the workflow detail, and no sentence is filler. It is dense and edges toward run-on in the mid-section covering the 48-hour handoff, but nothing is redundant.

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

Completeness5/5

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

An output schema exists, so return values need no explanation, and the description covers the prerequisites, the partner workflow and the user-facing side effect of an email link. For a 10-parameter mutating request tool, the agent has everything needed to call it and set expectations.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds provenance guidance: name, phone and message are optional and come from the user, which discourages fabricating them. It does not restate the origin/destination code semantics, which the schema already handles.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource — 'Requests confirmed charter prices from partner Villiers' — and scopes it to 'the route of a charter_alternative'. It immediately rules out the adjacent concept with 'NOT an empty leg: a regular charter', so an agent can separate it from the empty-leg siblings without reading a schema.

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

Usage Guidelines5/5

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

Gives an explicit precondition set: the user has seen the charter_alternative price range, asked for confirmed prices, and given their email. It also supplies an exclusion (not an empty leg) and states the dependency on charter_alternative for the route, leaving little to infer about when to call it.

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