Skip to main content
Glama

LocalSpot Trip

list_destinations

Every city LocalSpot Trip plans (Korea, Japan, Taiwan, Southeast Asia, Europe, Turkey, UAE, Egypt, Canada, USA, Mexico, Peru, Argentina, Brazil, Australia), with the trip lengths it has ready-made plans for. Optional country filter (e.g. japan, france, usa).

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": "list_destinations"
  }
}

Input Schema

NameRequiredDescriptionDefault
countryNoCountry slug or two-letter code, e.g. japan or JP (optional)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It discloses the shape of the result (cities paired with available trip lengths) and that filtering is optional, but says nothing about permissions, result size, or what an unfiltered call returns. For a low-risk listing operation this is adequate but thin.

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?

Two sentences, front-loaded with the core payload and followed by the filter note. The long parenthetical country list is informative but dense; the text is otherwise free of filler.

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 one-optional-parameter listing tool with no output schema and no annotations, the description covers what is returned and how filtering works. Only the relationship to sibling listing tools and result size limits are left unstated.

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% and the single country parameter already documents slug/two-letter-code forms with examples. The description's 'e.g. japan, france, usa' largely repeats that, adding no new syntax or matching behavior beyond the schema.

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 clearly states the resource: every destination city LocalSpot Trip covers, plus the trip lengths with ready-made plans. That is a specific, readable purpose. It does not, however, distinguish itself from the sibling list_cities, so an agent cannot tell from this text alone which of the two to call.

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?

Usage is only implied: the enumeration of covered destinations suggests browsing coverage or checking whether a country is supported. There is no explicit when-to-use statement and no named alternative (e.g. list_cities, request_city) for cases where the destination is absent.

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