Extralingo

get_course_details

Read-onlyIdempotent

Details for one course id from list_courses (pricing rows, supplements, metadata).

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
`course_id`	Yes	Course product id from list_courses.
`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.

Output Schema

Name	Required	Description	Default
`course`	No	Single course product with pricing rows and supplements for the requested start date.
`success`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 3, 2026

addedOutput schema / properties / course

Added value: +{
+  "additionalProperties": true,
+  "description": "Single course product with pricing rows and supplements for the requested start date.",
+  "type": [
+    "object",
+    "null"
+  ]
+}

removedOutput schema / properties / data

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

Changed10 schema fields changedOct 3, 2026

addedInput schema / properties / course_id / description
```
Added value: +"Course product id from list_courses."
```

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.5/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 fully covered structurally. The description adds a small amount of content context (that pricing rows and supplements come back), but says nothing about auth needs, rate limits, or behavior when the id is invalid.

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?

A single compact sentence with the identifying scope ('one course id') front-loaded and the returned content types in a trailing parenthetical. Nothing is wasted, though the fragment style makes it slightly clipped rather than fully self-explanatory.

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 covering return values and annotations covering the safety profile, the description only needs to fix scope and provenance, which it does. It is marginally thin on whether optional parameters like startDate or currency change the result, but nothing essential 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% and an output schema exists, so locale, currency, course_id, school_id and startDate are already fully documented, including the Craft CMS vs CRM id distinction. The description adds no syntax, default, or format detail beyond the schema; 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?

Names the resource (course details) and ties it to the sibling that supplies the id ('one course id from list_courses'), which separates it from list_courses and the other detail tools. It also enumerates the payload (pricing rows, supplements, metadata), though the verb is implied rather than 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 phrase 'from list_courses' implies the prerequisite step of enumerating courses first, and 'one course id' signals single-item scope. There is no explicit when-not guidance or comparison to alternatives such as get_trip or calculate_trip_price, so usage is only inferred.

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?