Extralingo

list_accommodations

Read-onlyIdempotent

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

Input Schema

TableJSON 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

TableJSON Schema

Name	Required	Description	Default
`data`	No
`success`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

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

A3.8/5.0

Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered. The description adds that returned groups carry ids used in save_trip, but it does not describe return shape, auth needs, rate limits, or pagination. With annotations covering the safety profile, a 3 is appropriate.

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 short sentences with zero waste; the purpose is front-loaded before the usage note. Every sentence earns its place, making the definition appropriately concise for an agent scanning tool options.

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 not be explained, and the annotations fully cover safety. The schema documents all parameters. The only minor gap is that the description does not explicitly differentiate this tool from get_accommodation_details, but given the rich structured data, it is complete enough.

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 five parameters in detail, including enums, examples, and defaults. The description adds no parameter-level guidance beyond implying that a school is required. Baseline 3 is correct 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?

The description identifies the resource ('Accommodation groups') and scope ('for a school'), but it omits an explicit verb and does not name the sibling tool get_accommodation_details to differentiate itself. It is still clear enough for an agent to understand that it lists accommodation groups rather than individual accommodation details.

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?

The second sentence gives a clear downstream usage: 'Use group ids in save_trip configuration (accommodationGroupId).' This tells the agent why to call it and where the result goes, but it does not mention when to prefer this tool over alternatives such as get_accommodation_details.

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?