Extralingo

search_language_schools

Read-onlyIdempotent

Search and rank language schools. Returns school_id, url, indicative from-price, and reviews. Prices are not a booking quote; call calculate_trip_price before quoting a total.

Input Schema

TableJSON Schema

Name	Required	Description
`city`	No	Single city slug filter. Prefer cities[] for multiple.
`limit`	No	Maximum schools to return (1–20).
`query`	No	Free-text search (school name, city, or keyword). Empty returns popular matches for the other filters.
`cities`	No	City slug filters from get_school_filters.
`locale`	No	Response language and site context. One of en, nl, da, sv.
`country`	No	Country slug or name filter from get_school_filters.
`language`	No	Language slug filter from get_school_filters (e.g. spanish, english).
`course_type`	No	Course type slug from get_school_filters (e.g. intensive, private).

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	No	Meilisearch-style payload with hits[] (school_id, title, url, city, country, pricing hints).
`success`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed13 schema fields changedOct 3, 2026

addedInput schema / properties / cities / description

Added value: +"City slug filters from get_school_filters."

addedInput schema / properties / cities / items / description
```
Added value: +"City slug."
```

addedInput schema / properties / city / description

Added value: +"Single city slug filter. Prefer cities[] for multiple."

addedInput schema / properties / country / description

Added value: +"Country slug or name filter from get_school_filters."

addedInput schema / properties / course_type / description

Added value: +"Course type slug from get_school_filters (e.g. intensive, private)."

changedInput schema / properties / language / description

Previous value: -"Language slug, e.g. spanish"New value: +"Language slug filter from get_school_filters (e.g. spanish, english)."

addedInput schema / properties / language / examples
```
Added value: +[
+  "spanish"
+]
```

addedInput schema / properties / limit / description

Added value: +"Maximum schools to return (1–20)."

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 / query / description

Added value: +"Free-text search (school name, city, or keyword). Empty returns popular matches for the other filters."

addedInput schema / properties / query / examples

Added value: +[
+  "Barcelona intensive Spanish"
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "data": {
+      "additionalProperties": true,
+      "description": "Meilisearch-style payload with hits[] (school_id, title, url, city, country, pricing hints).",
+      "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, and non-destructive behavior, so the safety profile is covered by structured data. The description adds value by disclosing the return fields (school_id, url, indicative from-price, reviews) and the critical caveat that prices are not a booking quote. That caveat is genuinely useful behavioral context not present in annotations. Still, it doesn't cover pagination, ranking logic, or empty-result behavior.

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 front-loaded sentences with zero waste: the first declares purpose and return shape, the second delivers the critical pricing caveat and points to the correct sibling. 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 correctly avoids re-explaining return structure, and the annotations cover safety hints. The pricing caveat and sibling routing are the key missing pieces an agent needs, so the essential behavioral guidance is there. Minor gaps remain around filter-selection strategy given the eight optional parameters, but nothing critical for correct invocation is absent.

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 coverage is 100%, so every parameter already has a description in the schema, including city vs cities preference and limit bounds. The description adds no filter syntax, slug source, or example usage beyond what the schema provides. Baseline 3 is appropriate when the schema does all the parameter work.

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 a specific verb+resource (search and rank language schools) and immediately distinguishes itself from the related pricing sibling by disclaiming that prices are not a booking quote and directing to calculate_trip_price. An agent can tell exactly what this tool does relative to get_school, list_courses, and calculate_trip_price.

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 description routes the agent to calculate_trip_price for totals, which is a clear when-to-use-nothing-else signal. However, it does not explain when to prefer this tool over get_school or search_destinations, nor how city vs cities vs query filters should be chosen. Usage is implied but not fully specified.

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?