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

TableJSON 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

TableJSON Schema

Name	Required	Description	Default
`lead`	No
`message`	No
`success`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

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 already declare openWorldHint=true, destructiveHint=false, idempotentHint=false. The description adds meaningful context beyond them: the required OAuth 'requests' scope and the optional idempotency key. Note the mild tension between idempotentHint=false and the idempotency_key surfaced via the schema, which is likely meant as opt-in replay protection rather than a true contradiction.

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?

Three short sentences, the trigger condition front-loaded ahead of the scope and idempotency notes. No filler or repetition of schema content.

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?

For an 8-parameter open-world mutation with nested objects, the description covers the call condition, auth requirement, and idempotency handling, and an output schema exists to explain returns. It does not describe side effects like notifying the school, but the essentials are present.

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 the schema already documents all 8 parameters (school_id, trip_id, configuration, contact, currency, etc.). The description only restates the optionality of idempotency_key and the account-sourced email, adding little beyond the structured data, so 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 and resource ('ask the school for a personal quote') and pins the trigger condition. Contrasted with the sibling create_booking by implication, so an agent can tell quoting apart from 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 when-to-use rule: 'when bookings_live is false or the student is not ready to book.' It does not explicitly name create_booking as the alternative or state exclusions, so it stops just short of a 5.

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?