Extralingo

get_school

Read-onlyIdempotent

School briefing: profile, cancellation policy, reviews, image URLs, bookings_live flag, and optional hero image for chat UI. Requires school_id from search_language_schools.

Input Schema

TableJSON Schema

Name	Required	Description
`locale`	No	Response language and site context. One of en, nl, da, sv.
`school_id`	Yes	Craft CMS school entry id from search_language_schools hits (field school_id). Not the CRM UUID.
`include_hero_image`	No	When true, structuredContent may include a compressed JPEG in MCP image content; hero_image is stripped from structuredContent after attach.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	No	School profile (title, url, city, country, bookings_live, reviews, images[]).
`success`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedOct 3, 2026

changedInput schema / properties / include_hero_image / description

Previous value: -"Include a compressed JPEG for display in chat. Default true."New value: +"When true, structuredContent may include a compressed JPEG in MCP image content; hero_image is stripped from structuredContent after attach."

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

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "data": {
+      "additionalProperties": true,
+      "description": "School profile (title, url, city, country, bookings_live, reviews, images[]).",
+      "type": "object"
+    },
+    "success": {
+      "const": true
+    }
+  },
+  "required": [
+    "success"
+  ],
+  "type": "object"
+}

First observedOct 3, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, so the safety burden is covered. The description adds context the annotations lack: the optional chat-UI hero image behavior and the instructional booking flag, which matter for how the result is consumed.

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 tight sentences with zero filler; the returned payload is front-loaded and the prerequisite follows. Nothing is redundant or padding.

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 shape need not be spelled out, and the description still enumerates the payload for quick routing. Only minor absence is any note on permissions or failure modes, which is acceptable given the complete annotations and output schema.

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 all three parameters (locale, school_id, include_hero_image) are fully documented in the schema, including the Craft CMS id sourcing and hero-image stripping. The description repeats the school_id requirement rather than adding syntax or format detail beyond it, so the baseline 3 applies.

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

Purpose5/5

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

States the resource (school briefing) and enumerates exactly what it returns: profile, cancellation policy, reviews, image URLs, bookings_live flag, and hero image. Distinguishes it from sibling getters like get_course_details and get_accommodation_details by naming school-specific content.

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?

Explicitly states the prerequisite sourcing: 'Requires school_id from search_language_schools,' which tells the agent it must call the search tool first. No explicit when-not or alternative-tool routing is given, but the ordering guidance is clear.

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?