Extralingo

request_discussion

Open a trip discussion thread with the school. 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`	No	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`	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 / 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 / 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 / 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

B3.2/5.0

Behavior3/5

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

Annotations already cover the safety profile (readOnlyHint=false, idempotentHint=false, openWorldHint=true, destructiveHint=false). The description adds one genuinely useful piece of context beyond annotations: the OAuth 'requests' scope requirement. It says nothing about what effect opening a thread has (does it notify/email the school, is it visible to the school immediately), which matters for a mutation-style call.

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 short sentences, action front-loaded, zero filler. It is efficient, though the trailing 'Optional idempotency_key' sentence adds no value beyond the schema and could be dropped.

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

Completeness3/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 not be described, and the schema carries the complex nested configuration shape. However, for a side-effecting request tool with 8 parameters and an open-world hint, the description omits what happens after the thread is opened and any prerequisites or failure modes, leaving it minimally viable rather than complete.

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 eight parameters including nested configuration, contact, and school_id sourcing. The description's only parameter remark, 'Optional idempotency_key', repeats what the schema states. Baseline 3 applies when the schema does the heavy lifting.

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?

States a specific verb and resource: 'Open a trip discussion thread with the school.' An agent can tell what the tool produces. It does not, however, distinguish itself from the near-duplicate sibling ask_school_question or from request_quote, so the sibling differentiation credit is not earned.

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

Usage Guidelines2/5

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

No when-to-use or when-not-to-use guidance is given. With siblings like ask_school_question, request_quote, and create_booking, the agent has no stated basis for choosing this tool over those; the reader must infer the routing from the name alone.

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?