Skip to main content
Glama

Find destinations

resolve_destination
Read-onlyIdempotent

Find a supported Guestit destination in Sweden before searching apartments and holiday homes. Pass the city or area alone, such as Åre or Stockholm. Returns only places with Guestit stays, at most one. When nothing matches, ask the user about a larger place nearby.

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": {
      "query": "<query>"
    },
    "name": "resolve_destination"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYes
localeNoen

Output Schema

NameRequiredDescriptionDefault
viewYes
staysYes
localeYesen
paginationYes
destinationsYes
calculated_atYes
requested_stayYes
applied_filtersYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

The annotations already establish a safe, idempotent, closed-world read, so the description is not carrying the safety burden. It adds genuinely new behavior: results are limited to places with Guestit inventory, at most one is returned, and a no-match outcome should trigger a clarification question rather than a retry.

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?

Four short sentences, front-loaded with purpose, then input format, then result cardinality, then failure handling. Nothing is repeated and no sentence is filler.

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

Completeness5/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 structure need not be described; the description still adds the one fact an agent needs about results (at most one match). Purpose, input shape, cardinality and no-match handling are all covered for a simple two-parameter resolver.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage the description must carry parameter meaning, and "pass the city or area alone, such as Åre or Stockholm" does real work — it rules out addresses, hotel names and country strings that would otherwise look valid for a free-text query. The locale parameter is left unexplained, though its en/sv enum and default make it largely self-evident.

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?

"Find a supported Guestit destination in Sweden" gives a specific verb, resource and geographic scope, and the clause "before searching apartments and holiday homes" positions it as the lookup step rather than the search step. An agent can distinguish it from search_stays/compare_stays without opening any schema.

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?

Explicit sequencing guidance ("before searching apartments and holiday homes") plus an input constraint ("pass the city or area alone") and a fallback instruction for no-match cases ("ask the user about a larger place nearby"). It never names a concrete sibling as the alternative to use instead, so it stops short of full when/when-not routing.

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.

Resources