Extralingo

search_destinations

Read-onlyIdempotent

Search cities, countries, and school names. Use before search_language_schools to resolve place names to slugs.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Maximum results (1–20).
`query`	No	Destination or school name prefix. Empty returns popular destinations.
`locale`	No	Response language and site context. One of en, nl, da, sv.
`language`	No	Optional language slug to restrict destinations (e.g. spanish).

Output Schema

TableJSON Schema

Name	Required	Description
`hits`	No	Destination matches.
`query`	No
`locale`	No
`schools`	No	Optional school name fallback hits.
`success`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedOct 3, 2026

addedInput schema / properties / language / description

Added value: +"Optional language slug to restrict destinations (e.g. spanish)."

addedInput schema / properties / limit / description
```
Added value: +"Maximum results (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: +"Destination or school name prefix. Empty returns popular destinations."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "hits": {
+      "description": "Destination matches.",
+      "items": {
+        "additionalProperties": true,
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "locale": {
+      "enum": [
+        "en",
+        "nl",
+        "da",
+        "sv"
+      ],
+      "type": "string"
+    },
+    "query": {
+      "type": "string"
+    },
+    "schools": {
+      "description": "Optional school name fallback hits.",
+      "items": {
+        "additionalProperties": true,
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "success": {
+      "const": true
+    }
+  },
+  "required": [
+    "success"
+  ],
+  "type": "object"
+}

First observedOct 3, 2026

TDQS

A4.2/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds the useful hint that output is intended as slugs for a downstream call, but says nothing about result format, empty-query behavior, or ranking beyond what the schema states. Adequate, not rich.

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 waste, with the primary purpose front-loaded and the sequencing hint second. Nothing to trim.

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 and the input schema is fully documented, so return values and parameter meanings need not be restated. The description covers what it searches and when to call it; only minor context (e.g. how many slugs to resolve or that locale controls response language) is left 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 all four parameters (query, locale, language, limit) are already documented in the schema, including the empty-query fallback and the language-slug filter. The description adds no parameter detail, so the baseline of 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 a specific verb (Search) over concrete resources (cities, countries, school names), and explicitly distinguishes itself from the sibling search_language_schools. An agent can tell what this does without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Gives an explicit ordering rule: use this before search_language_schools to resolve place names to slugs. Names the alternative tool and the condition that selects it, so the routing decision is unambiguous.

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?