Skip to main content
Glama

Extralingo

by com.extralingo
OverviewDiscussionsAdmin

get_accommodation_details

Read-onlyIdempotent

Details for one accommodation group id from list_accommodations.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
localeNoResponse language and site context. One of en, nl, da, sv.
currencyNoISO 4217 currency for prices in this call. Usually EUR.EUR
group_idYesAccommodation group id from list_accommodations.
startDateNoCourse start calendar date (YYYY-MM-DD). Typically a Monday from list_starting_dates.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataNo
successYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changed
    • 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 / group_id / description
      Added value: +"Accommodation group id from list_accommodations."
    • 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 / 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"
+}
  2. First observed

TDQS

B3.2/5.0
Behavior2/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 no behavioral context of its own — nothing about how startDate/currency affect returned pricing or availability, or about error behavior for an unknown group id.

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 front-loaded sentence with no filler, and the key dependency (the id source) is stated immediately. It is arguably over-terse rather than padded, but nothing is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 values need no explanation, and the required parameter is obvious. However, the tool accepts locale, currency and startDate that plausibly change results, and the description gives no hint that details are context/date-dependent — a meaningful gap for a lookup tool.

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 are already documented in the schema (including the group_id provenance and the date/currency semantics). The description's only nod is 'from list_accommodations', which merely repeats the schema's own wording; 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?

The description names a specific resource ('accommodation group') and the operation ('details'), and ties it to the sibling that produces the id. An agent can tell it apart from list_accommodations, though the phrase 'Details for' is less precise than an explicit verb like 'retrieve full details'.

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 implies the workflow (call list_accommodations first, then fetch details for one group id) but never states when to use this versus alternatives, nor any exclusions. Usage is inferable rather than spelled out.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Extralingo toolsInspect
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