Extralingo

list_accommodations

Read-onlyIdempotent

Accommodation groups for a school. Use group ids in save_trip configuration (accommodationGroupId).

Input Schema

Name	Required	Description	Default
`locale`	No	Response language and site context. One of en, nl, da, sv.
`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.
`startDate`	No	Course start calendar date (YYYY-MM-DD). Typically a Monday from list_starting_dates.
`country_code`	No	Visitor country ISO 3166-1 alpha-2 (e.g. NL). Affects fee display where applicable.

Output Schema

Name	Required	Description
`school`	No
`success`	Yes
`currency`	No
`start_date`	No
`location_discount`	No
`busy_school_months`	No
`accommodation_groups`	No	Flat list of accommodation groups (id for get_accommodation_details / configuration).
`has_location_discounts`	No
`accommodation_categories`	No	Same groups nested by category for display.
`allows_double_room_individual_bookings`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed10 schema fields changedOct 3, 2026

addedOutput schema / properties / accommodation_categories

Added value: +{
+  "description": "Same groups nested by category for display.",
+  "items": {
+    "additionalProperties": true,
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / accommodation_groups

Added value: +{
+  "description": "Flat list of accommodation groups (id for get_accommodation_details / configuration).",
+  "items": {
+    "additionalProperties": true,
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / allows_double_room_individual_bookings
```
Added value: +{
+  "type": "boolean"
+}
```

addedOutput schema / properties / busy_school_months

Added value: +{
+  "additionalProperties": true,
+  "type": [
+    "object",
+    "null"
+  ]
+}

addedOutput schema / properties / currency
```
Added value: +{
+  "type": "string"
+}
```

removedOutput schema / properties / data

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

addedOutput schema / properties / has_location_discounts
```
Added value: +{
+  "type": "boolean"
+}
```

addedOutput schema / properties / location_discount

Added value: +{
+  "additionalProperties": true,
+  "type": [
+    "object",
+    "null"
+  ]
+}

addedOutput schema / properties / school

Added value: +{
+  "additionalProperties": true,
+  "type": [
+    "object",
+    "null"
+  ]
+}

addedOutput schema / properties / start_date
```
Added value: +{
+  "type": "string"
+}
```

Changed11 schema fields changedOct 3, 2026

addedInput schema / properties / country_code / description

Added value: +"Visitor country ISO 3166-1 alpha-2 (e.g. NL). Affects fee display where applicable."

addedInput schema / properties / country_code / examples
```
Added value: +[
+  "NL",
+  "DE"
+]
```

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 / locale / description

Added value: +"Response language and site context. One of en, nl, da, sv."

addedInput schema / properties / locale / examples

Added value: +[
+  "en",
+  "nl",
+  "da",
+  "sv"
+]

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 / startDate / description

Added value: +"Course start calendar date (YYYY-MM-DD). Typically a Monday from list_starting_dates."

addedInput schema / properties / startDate / examples
```
Added value: +[
+  "2026-09-07"
+]
```

changedOutput schema / (root)

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

First observedOct 3, 2026

TDQS

B3.1/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds the scoping fact that results are per-school and that the ids feed save_trip, but says nothing about pagination, filtering, or how many groups to expect. With annotations carrying the safety burden, this is an adequate 3.

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?

Two short sentences with zero padding, and the resource is stated before the downstream integration tip. It is appropriately sized, though the first sentence is a fragment rather than a complete statement of what the call returns.

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?

With an output schema present and 100% schema coverage, the description does not need to describe return values or parameter formats. What is missing is the when-to-use boundary against sibling tools like get_accommodation_details and how this fits with get_school, leaving the definition adequate but not complete for a 17-tool catalog.

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 (school_id, locale, currency, startDate, country_code) is documented in the schema, including cross-tool references like search_language_schools and list_starting_dates. The description adds no parameter-level information whatsoever, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the resource ('Accommodation groups for a school'), which is enough to distinguish it from get_accommodation_details (single accommodation details), but it never states the action verb. It's a noun phrase where 'list' is only implied by the tool name, so the purpose is clear but not crisply stated.

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 second sentence is a downstream usage hint: 'Use group ids in save_trip configuration (accommodationGroupId).' That tells the agent why/when to call this (to obtain ids for save_trip), which is genuinely useful. However, it gives no exclusion or comparison against get_accommodation_details or get_school, so the routing guidance is only partial.

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?