Skip to main content
Glama

Search Sailing Destinations

search_locations
Read-only

Find marinas, harbours and anchorages three ways: by NAME (q), by POPULARITY within an area (region/country/city — ranked on observed AIS vessel traffic for a month), or by REACH from a place you already have (from + within_nm) — where boats are actually recorded sailing to from there, with measured passage times. Use from for "where can I sail from X", "what is a day sail from X", "somewhere quieter nearby". Provide q, or an area, or from.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_locations"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoName search (min 2 chars). Optional when an area filter is given.
cityNo
fromNoOrigin location id (or slug) to sail FROM — take it from an earlier search_locations or get_location_details result. Returns places boats were tracked sailing to from there.
sortNoDefault popularity = real vessel traffic for the month; boats = charter fleet size; rating = Google rating
typeNoKind of place — e.g. anchorage for "quiet bays"; spot = an unclassified stop (beach, spit, headland)
limitNo
monthNoMonth to rank popularity for (default: current month)
regionNoSailing region as the guest says it: Dalmatia, Istria, Kvarner, the Ionian, the Saronic, the Cyclades, the Dodecanese, the Sporades
countryNoCountry name or 2-letter code
currencyNoOptional: the currency every amount in the answer is written in, and any price you send is read in. When the conversation has its own currency, that one is used whatever is sent; otherwise the one sent, EUR when omitted.
within_nmNoHow far, in nautical miles, for a "from" search. Default 35. Pick the ring by time — a charter boat makes about 6 knots, plus 30 minutes to leave and arrive, so: 10nm ≈ 2.2h, 20nm ≈ 3.8h, 35nm ≈ 6.3h, 55nm ≈ 9.7h, 100nm ≈ 17.2h. A full charter day of sailing is roughly 6-8h, which makes 35nm a comfortable day sail and 55nm a long one.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / currency / description
      Previous value: -"Optional: the currency every amount in the answer is written in, and any price you send is read in. EUR when omitted."New value: +"Optional: the currency every amount in the answer is written in, and any price you send is read in. When the conversation has its own currency, that one is used whatever is sent; otherwise the one sent, EUR when omitted."
  2. Changed1 schema field changed
    • addedInput schema / properties / currency
      Added value: +{
      +  "description": "Optional: the currency every amount in the answer is written in, and any price you send is read in. EUR when omitted.",
      +  "enum": [
      +    "EUR",
      +    "USD"
      +  ],
      +  "type": "string"
      +}
  3. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint true, destructiveHint false, openWorldHint false), so the description only needs to add context, and it does: popularity is ranked on observed AIS vessel traffic for a month, and reach results carry measured passage times rather than straight-line distances. It does not discuss result volume beyond the schema's limit/max 20, which keeps it short of a 5.

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?

Front-loaded with the three modes in capital letters, then the routing examples, then the one-line requirement. It is dense and readable with no filler, though the em-dash and parenthetical nesting make it slightly heavier than it needs to be.

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 an 11-parameter, zero-required search tool with no output schema, the description covers mode selection, ranking basis, and the reach mechanic well enough to call correctly. It leaves return shape and result ordering under `sort` to the schema, which is acceptable but leaves a small gap.

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?

Schema coverage is 82%, so the baseline is 3, but the description adds cross-parameter meaning the schema cannot: that q, area, and `from` are alternative entry points, and that `within_nm` is chosen by passage time rather than distance. Some semantics (sort, type, month) live only in the schema, so it does not fully supersede it.

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?

The description gives a specific verb (find) and resource (marinas, harbours, anchorages) and splits the tool into three clearly named modes — NAME (q), POPULARITY by area, and REACH from a place via `from` + `within_nm`. That structure makes it distinguishable from siblings such as search_pois, search_routes, and get_location_details without opening schemas.

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?

It states the selection rule explicitly ('Provide q, or an area, or from') and maps natural-language intents to the `from` mode: 'where can I sail from X', 'what is a day sail from X', 'somewhere quieter nearby'. The note to pull `from` from an earlier search_locations or get_location_details result gives a concrete workflow prerequisite.

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.