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

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
+]
```

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.6/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 openWorldHint=false, so the safety profile is covered. The description adds the 'Live' freshness signal, which is real value, but says nothing about pagination, result size, or whether the catalogue is scoped to a single school.

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 no filler; the identity of the resource is front-loaded and the usage hint follows immediately. Every clause 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?

An output schema exists, so return-value explanation is not required, and the description still names the salient returned fields. Combined with full schema coverage, an agent has enough to call this correctly; only cross-sibling disambiguation is missing.

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 (school_id, locale, currency, startDate, country_code) is already documented in the schema with examples and cross-references. The description adds no parameter-level detail, which is acceptable at this coverage level but earns no extra credit.

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 the resource precisely ('Live course catalogue for a bookings_live school') and even names the key returned fields (course ids, weeks, prices), so an agent knows what it gets back. It does not explicitly differentiate itself from siblings like get_course_details or list_starting_dates, which is the only thing keeping it from 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 Guidelines3/5

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

It gives a downstream routing hint ('Use returned course ids inside save_trip configuration'), which is genuinely useful. However it never states when to call this versus get_course_details or list_starting_dates, so the selection guidance is implied rather than explicit.

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?