easygroupflights

Send a group flight quote request

egf_request_group_quote

Sends a prepared group flight enquiry to a human specialist, who replies by email with a written quote, usually within about 2 hours. Takes only the confirmation_token from preparing it; it returns a confirmation, not a price, and books or charges nothing.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`idempotency_key`	No	Optional. Any unique string for this request, such as a UUID. Calling again with the same key and the same arguments returns the first result instead of sending again. Kept for 24 hours.
`confirmation_token`	Yes	confirmation_token returned when this write was prepared. Valid for 15 minutes.

Output Schema

TableJSON Schema

Name	Required	Description
`cabin`	Yes
`seats`	Yes	Seated travellers; lap infants excluded.
`adults`	Yes
`domain`	Yes	The market whose desk handles the enquiry.
`market`	Yes
`origin`	Yes
`status`	Yes	The enquiry reached the specialist desk. Nothing is booked or charged.
`youths`	Yes
`infants`	Yes
`children`	Yes
`reply_to`	Yes	Where the quote will be emailed.
`destination`	Yes
`return_date`	No	ISO 8601 date (YYYY-MM-DD). Absent for one way.
`departure_date`	Yes	ISO 8601 date (YYYY-MM-DD).
`max_reply_hours`	Yes
`typical_reply_hours`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed24 schema fields changedOct 1, 2026

removedInput schema / properties / adults

Removed value: -{
-  "description": "Travellers aged 16 or over.",
-  "minimum": 1,
-  "type": "integer"
-}

removedInput schema / properties / cabin_class

Removed value: -{
-  "description": "Defaults to economy.",
-  "enum": [
-    "economy",
-    "business"
-  ],
-  "type": "string"
-}

removedInput schema / properties / children

Removed value: -{
-  "description": "Travellers aged 2–11, each in their own seat.",
-  "minimum": 0,
-  "type": "integer"
-}

removedInput schema / properties / children_ages

Removed value: -{
-  "description": "Age of each child, one entry per child.",
-  "items": {
-    "type": "integer"
-  },
-  "type": "array"
-}

addedInput schema / properties / confirmation_token

Added value: +{
+  "description": "confirmation_token returned when this write was prepared. Valid for 15 minutes.",
+  "type": "string"
+}

removedInput schema / properties / date_flexibility_days

Removed value: -{
-  "description": "How many days either side of the given dates the group can move. 0 means fixed dates.",
-  "minimum": 0,
-  "type": "integer"
-}

removedInput schema / properties / departure_date

Removed value: -{
-  "description": "Outbound date, YYYY-MM-DD.",
-  "type": "string"
-}

removedInput schema / properties / destination

Removed value: -{
-  "description": "Arrival airport as an IATA code, e.g. [\"BCN\"].",
-  "items": {
-    "pattern": "^[A-Za-z]{3}$",
-    "type": "string"
-  },
-  "type": "array"
-}

removedInput schema / properties / email

Removed value: -{
-  "description": "Where the quote is sent. Required.",
-  "type": "string"
-}

removedInput schema / properties / first_name

Removed value: -{
-  "description": "Organiser's first name.",
-  "type": "string"
-}

removedInput schema / properties / infants

Removed value: -{
-  "description": "Under 2, travelling on an adult lap. They do not occupy a seat and do not count towards the group of 10.",
-  "minimum": 0,
-  "type": "integer"
-}

removedInput schema / properties / last_name

Removed value: -{
-  "description": "Organiser's surname.",
-  "type": "string"
-}

removedInput schema / properties / market

Removed value: -{
-  "description": "Which market handles the enquiry: en (easygroupflights.com), pl (grupoweloty.pl) or at (gruppenfluege.at). Defaults to en.",
-  "enum": [
-    "en",
-    "pl",
-    "at"
-  ],
-  "type": "string"
-}

removedInput schema / properties / note

Removed value: -{
-  "description": "Anything that shapes the fare: what the group is (school trip, wedding, sports team, conference), baggage or equipment needs, budget, who pays, whether names are known yet.",
-  "type": "string"
-}

removedInput schema / properties / origin

Removed value: -{
-  "description": "Departure airport as an IATA code, e.g. [\"LHR\"]. Several codes are allowed when the group converges from more than one city.",
-  "items": {
-    "pattern": "^[A-Za-z]{3}$",
-    "type": "string"
-  },
-  "type": "array"
-}

removedInput schema / properties / phone

Removed value: -{
-  "description": "Contact number in international form, e.g. +441244568183. Required — the agent may call to confirm details.",
-  "type": "string"
-}

removedInput schema / properties / return_date

Removed value: -{
-  "description": "Return date, YYYY-MM-DD. Omit for a one-way group booking.",
-  "type": "string"
-}

removedInput schema / properties / return_destination

Removed value: -{
-  "description": "Return leg arrival airports, if travellers go home to a different city.",
-  "items": {
-    "type": "string"
-  },
-  "type": "array"
-}

removedInput schema / properties / return_origin

Removed value: -{
-  "description": "Return leg departure airports, if the group flies home from somewhere other than the destination.",
-  "items": {
-    "type": "string"
-  },
-  "type": "array"
-}

removedInput schema / properties / youths

Removed value: -{
-  "description": "Travellers aged 12–15.",
-  "minimum": 0,
-  "type": "integer"
-}

removedInput schema / properties / youths_ages

Removed value: -{
-  "description": "Age of each youth, one entry per youth.",
-  "items": {
-    "type": "integer"
-  },
-  "type": "array"
-}

changedInput schema / required

Previous value: -[
-  "origin",
-  "destination",
-  "departure_date",
-  "adults",
-  "email",
-  "phone"
-]New value: +[
+  "confirmation_token"
+]

changedOutput schema / properties / departure_date / description

Previous value: -"YYYY-MM-DD."New value: +"ISO 8601 date (YYYY-MM-DD)."

changedOutput schema / properties / return_date / description

Previous value: -"YYYY-MM-DD. Absent for one way."New value: +"ISO 8601 date (YYYY-MM-DD). Absent for one way."

AddedOct 1, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the annotations (non-read-only, open-world, non-destructive, not idempotent), the description discloses that delivery goes to a human specialist by email, the expected turnaround of about 2 hours, and that it neither books nor charges. These are substantive behavioral facts an agent cannot infer from the structured fields.

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 filler, front-loading what the tool does and following with the key constraint and the no-charge clarification. Every clause carries information.

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?

For a single-required-param write tool with an output schema present, the description supplies the missing flow context (prepare-then-send), the async human turnaround, and the side-effect boundaries. Nothing an agent needs to invoke it correctly is absent.

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 parameters are already documented, giving a baseline of 3. The description adds flow-level meaning by stating the confirmation_token must originate from the prepare call and that it is the only input taken, which helps the agent chain the two tools correctly.

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 (sends) and resource (a prepared group flight enquiry), and the word "prepared" plus "confirmation_token from preparing it" clearly distinguishes it from the sibling egf_prepare_group_quote. An agent can tell this is the send step of a two-phase flow without opening the schema.

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

Usage Guidelines4/5

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

It establishes the precondition that a prepare step must have run first ("Takes only the confirmation_token from preparing it") and clarifies the outcome boundary (returns confirmation, not a price, books or charges nothing). It does not explicitly name egf_prepare_group_quote as the required precursor, so the routing is left slightly implicit.

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

All easygroupflights tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.