Extralingo

list_courses

Read-onlyIdempotent

Live course catalogue for a bookings_live school (course ids, weeks, prices). Use returned course ids inside save_trip configuration.

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	School metadata from the booking API.
`success`	Yes
`currency`	No
`start_date`	No	Effective start date used for pricing (YYYY-MM-DD).
`course_types`	No	Course types with nested courses[] (course ids, weeks, week prices).
`pricing_rule`	No
`location_discount`	No
`busy_school_months`	No
`has_location_discounts`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed9 schema fields changedOct 3, 2026

addedOutput schema / properties / busy_school_months

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

addedOutput schema / properties / course_types

Added value: +{
+  "description": "Course types with nested courses[] (course ids, weeks, week prices).",
+  "items": {
+    "additionalProperties": true,
+    "type": "object"
+  },
+  "type": "array"
+}

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 / pricing_rule

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

addedOutput schema / properties / school

Added value: +{
+  "additionalProperties": true,
+  "description": "School metadata from the booking API.",
+  "type": [
+    "object",
+    "null"
+  ]
+}

addedOutput schema / properties / start_date

Added value: +{
+  "description": "Effective start date used for pricing (YYYY-MM-DD).",
+  "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
+]
```

changedInput schema / properties / startDate / description

Previous value: -"YYYY-MM-DD Monday"New 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?

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed world, so the safety profile is covered. The description adds that the catalogue is 'live' and lists the returned fields, but says nothing about pagination, filtering behavior, or auth needs.

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, zero filler, with the resource and its returned fields front-loaded before the chaining instruction. Every sentence earns its place.

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?

With an output schema present the description need not explain return values, and the schema fully documents all five parameters. The only missing piece is how this list relates to get_course_details, which the description leaves implicit.

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 documented in the schema (locale, currency, school_id source, startDate, country_code). The description adds no syntax or format meaning beyond what the schema already provides, so the 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?

States a specific verb and resource ('Live course catalogue for a bookings_live school') and even names the fields returned (course ids, weeks, prices). It does not explicitly distinguish itself from the sibling get_course_details, so it falls just short of a 5.

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 explicit downstream context: the returned course ids are meant to be fed into save_trip configuration, which tells an agent when this tool belongs in a workflow. It names no exclusion or alternative (e.g. get_course_details for a single course), so it is clear context without routing guidance.

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?