Extralingo

ask_school_question

Send a question to the school without a full trip configuration. 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.
`message`	Yes	Student message to the school.
`trip_id`	No	Optional trip_id from save_trip.
`currency`	No	ISO 4217 currency for prices in this call. Usually EUR.	EUR
`school_id`	Yes	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.

Changed12 schema fields changedOct 3, 2026

removedInput schema / properties / auth_token
```
Removed value: -{
-  "type": "string"
-}
```

addedInput schema / properties / configuration

Added value: +{
+  "additionalProperties": true,
+  "description": "Same shape as the Extralingo school-page configurator: startDate (YYYY-MM-DD), students[] with courseId, weeks, optional accommodationGroupId, mealType, extras.",
+  "properties": {
+    "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"
+    }
+  },
+  "type": "object"
+}

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 / message / description
```
Added value: +"Student message to the school."
```

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

Added value: +{
+  "description": "Optional trip_id from save_trip.",
+  "type": "string"
+}

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

A3.7/5.0

Behavior4/5

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

Annotations cover the safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=true), and the description adds a genuinely non-structured fact: the OAuth 'requests' scope requirement. It also surfaces idempotency_key as optional, though the 24-hour replay semantics live only in the schema.

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?

Three front-loaded fragments, zero filler, and the distinguishing constraint appears first. It reads as terse notes rather than prose, but nothing wastes the agent's attention.

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?

An output schema exists, so return values need no explanation, and annotations carry the safety profile. Given 8 parameters with nested objects, the description adequately covers the mutation plus auth, though the mild tension between 'without a full trip configuration' and the optional full configuration object could confuse an agent choosing whether to supply it.

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 every parameter is already documented (school_id provenance, configuration shape, currency, idempotency window). The description only restates idempotency_key's optionality, adding no meaning beyond the schema; baseline 3 applies.

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?

Specific verb+resource (send a question to the school) with a scope qualifier: 'without a full trip configuration' separates it from save_trip/create_booking flows. It stops short of naming the nearest siblings (request_discussion, request_quote, email_trip), so an agent still has to infer which contact channel applies.

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

Usage Guidelines3/5

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

The phrase 'without a full trip configuration' implies the lightweight-contact scenario, which is real guidance. However, no alternative is named and no when-not condition is given, despite three sibling tools (request_discussion, request_quote, email_trip) that plausibly compete for the same intent.

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?