Skip to main content
Glama

Destination facts

get_destination
Read-onlyIdempotent

What a destination offers: networks, data sizes, validity options, whether unlimited day passes and top ups exist, the starting price, and what the traveler needs to know.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "destination_id": "<destination_id>"
    },
    "name": "get_destination"
  }
}

Input Schema

NameRequiredDescriptionDefault
currencyNoISO 4217 code for prices, e.g. EUR, GBP, JPY. Defaults to USD.
languageNoLanguage of the buy link and of region names: en, it, es, fr, de, pl, pt, tr. Defaults to en.
destination_idYesDestination id from search_destinations, e.g. "jp" or "eu-42".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered without the description. The description's contribution is the content profile — what categories of information come back — which is useful given there is no output schema, but it says nothing about behavior for unknown destination ids, error shapes, or whether prices are cached/live.

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 no filler, and the highest-value item (prices) lands near the end of the enumeration. It reads as a noun-phrase fragment rather than a full statement of action, but nothing is wasted.

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?

For a simple read-only lookup with a fully documented three-parameter schema, the description is nearly sufficient, and its enumeration of returned facts substitutes for the absent output schema. Only the failure/edge-case behavior for a bad destination id is left unstated, which is minor at this complexity.

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%: all three parameters carry descriptions, including the ISO 4217 pattern for currency, the supported language list, and the example destination ids. The description adds no parameter-level meaning beyond that, so the baseline of 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 the resource (a destination) and enumerates the specific facts it returns: networks, data sizes, validity options, unlimited day passes, top-ups, and starting price. That is a concrete content profile rather than a restatement of the name. It stops short of any explicit contrast with siblings such as search_destinations or get_quote, so an agent must infer the boundary itself.

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

Usage Guidelines2/5

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

The description contains no when-to-use guidance, no prerequisites, and no mention of alternatives. Nothing tells the agent that a destination id should first come from search_destinations, or when to prefer this over get_quote or list_plans — that routing hint exists only in the schema's destination_id field, not in the description.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.