Extralingo

request_quote

Ask the school for a personal quote when bookings_live is false or the student is not ready to book. Requires OAuth requests scope. Optional idempotency_key.

Input Schema

Name	Required	Description	Default
`contact`	No	Optional first_name, last_name. Email always comes from the verified account.
`trip_id`	No	Optional trip_id from save_trip.
`comments`	No	Student message to the school.
`currency`	No	ISO 4217 currency for prices in this call. Usually EUR.	EUR
`school_id`	No	Craft CMS school entry id from search_language_schools hits (field school_id). Not the CRM UUID.
`configuration`	No	Same shape as the Extralingo school-page configurator: startDate (YYYY-MM-DD), students[] with courseId, weeks, optional accommodationGroupId, mealType, extras.
`idempotencyKey`	No	Optional alias of idempotency_key.
`idempotency_key`	No	Optional. Same semantics as create_booking (24 hour replay window).

Output Schema

Name	Required	Description
`kind`	No	Lead type on success.
`message`	No	Human-readable confirmation (not a booking confirmation).
`success`	Yes
`redirectUrl`	No	Extralingo /my URL for the student to follow the request, when available.
`newBookingId`	No	Craft newBookings entry id when created.

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedOct 3, 2026

addedOutput schema / properties / kind

Added value: +{
+  "description": "Lead type on success.",
+  "enum": [
+    "quote"
+  ],
+  "type": "string"
+}

removedOutput schema / properties / lead

Removed value: -{
-  "additionalProperties": true,
-  "type": "object"
-}

addedOutput schema / properties / message / description

Added value: +"Human-readable confirmation (not a booking confirmation)."

addedOutput schema / properties / newBookingId

Added value: +{
+  "description": "Craft newBookings entry id when created.",
+  "type": [
+    "integer",
+    "null"
+  ]
+}

addedOutput schema / properties / redirectUrl

Added value: +{
+  "description": "Extralingo /my URL for the student to follow the request, when available.",
+  "type": [
+    "string",
+    "null"
+  ]
+}

Changed14 schema fields changedOct 3, 2026

removedInput schema / properties / auth_token
```
Removed value: -{
-  "type": "string"
-}
```
addedInput schema / properties / comments / description
```
Added value: +"Student message to the school."
```
addedInput schema / properties / configuration / additionalProperties
```
Added value: +true
```

addedInput schema / properties / configuration / description

Added value: +"Same shape as the Extralingo school-page configurator: startDate (YYYY-MM-DD), students[] with courseId, weeks, optional accommodationGroupId, mealType, extras."

addedInput schema / properties / configuration / properties

Added value: +{
+  "accommodationGroupId": {
+    "description": "Accommodation group id from list_accommodations (optional).",
+    "type": "string"
+  },
+  "mealType": {
+    "description": "Meal plan key when accommodation is selected.",
+    "type": "string"
+  },
+  "startDate": {
+    "description": "Course start calendar date (YYYY-MM-DD). Typically a Monday from list_starting_dates.",
+    "examples": [
+      "2026-09-07"
+    ],
+    "type": "string"
+  },
+  "students": {
+    "description": "One object per traveller. courseId comes from list_courses.",
+    "items": {
+      "additionalProperties": true,
+      "properties": {
+        "courseId": {
+          "description": "Course product id from list_courses for this school.",
+          "type": "string"
+        },
+        "weeks": {
+          "description": "Course duration in weeks.",
+          "minimum": 1,
+          "type": "integer"
+        }
+      },
+      "type": "object"
+    },
+    "type": "array"
+  }
+}

addedInput schema / properties / contact / additionalProperties
```
Added value: +true
```

changedInput schema / properties / contact / description

Previous value: -"Optional first_name, last_name. Email always comes from the verified account. A different contact.email is rejected."New value: +"Optional first_name, last_name. Email always comes from the verified account."

addedInput schema / properties / currency / description

Added value: +"ISO 4217 currency for prices in this call. Usually EUR."

addedInput schema / properties / currency / examples
```
Added value: +[
+  "EUR"
+]
```
addedInput schema / properties / idempotencyKey / description
```
Added value: +"Optional alias of idempotency_key."
```

addedInput schema / properties / school_id / description

Added value: +"Craft CMS school entry id from search_language_schools hits (field school_id). Not the CRM UUID."

addedInput schema / properties / school_id / examples
```
Added value: +[
+  12345
+]
```
addedInput schema / properties / trip_id / description
```
Added value: +"Optional trip_id from save_trip."
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "lead": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "message": {
+      "type": "string"
+    },
+    "success": {
+      "const": true
+    }
+  },
+  "required": [
+    "success"
+  ],
+  "type": "object"
+}

Changed2 schema fields changedOct 3, 2026

addedInput schema / properties / idempotencyKey
```
Added value: +{
+  "type": "string"
+}
```

addedInput schema / properties / idempotency_key

Added value: +{
+  "description": "Optional. Same semantics as create_booking (24 hour replay window).",
+  "type": "string"
+}

First observedOct 3, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations declare the mutation/safety profile (readOnlyHint=false, openWorldHint=true, destructiveHint=false), and the description usefully adds the OAuth 'requests' scope requirement, which annotations do not convey. Idempotency-key behavior is deferred to the schema, so it adds only moderate extra behavioral context.

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 sentences, no waste, and the critical call condition is front-loaded before the incidental scope/idempotency notes. Nothing needs trimming.

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?

With an output schema present and full schema coverage on 8 parameters, the description only needs to carry the when-to-call and auth context, which it does. It is slightly thin on how the quote is delivered or whether the request is free/side-effecting, but not enough to mislead.

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% and every parameter, including the nested configuration object, is documented richly in the schema. The description adds nothing beyond noting idempotency_key is optional, so the baseline 3 applies.

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+resource ('Ask the school for a personal quote') and immediately bounds the scenario ('when bookings_live is false or the student is not ready to book'), which distinguishes it from the booking/creating siblings. An agent can tell this apart from create_booking without opening either 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?

Gives a clear trigger condition (bookings_live false, student not ready to book) rather than terse context. It stops short of naming the closest siblings it should be chosen over — request_discussion, ask_school_question, create_booking — so the boundary with those is left to inference.

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

All Extralingo 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.

Resources

Need Help?