Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

klook_destinations

List Klook countries and destination-guide areas, including city IDs and listing URLs, so you can pick a city_id and browse bookable options via /klook/search.

Instructions

List Klook countries and destination areas. Returns Klook's bookable country list and its destination-guide area tree with city ids and listing URLs. Use a city_id with /klook/search to browse that destination.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden and does disclose the response shape: a country list plus an area tree carrying city ids and listing URLs. It stops short of anything about the call itself — no caching, payload size, rate limits, or failure behavior — for what is an unannotated network-backed lookup.

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?

Three short sentences, front-loaded with the verb+resource, followed by return contents and then the follow-on action. The only mild overlap is between sentence one and the country-list restatement in sentence two, which buys precision rather than waste.

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 zero-parameter discovery tool with no output schema, the description covers what is returned and how to act on it, which is the essential contract. What is missing is minor: whether the area tree is nested or flat, and what an empty or partial result looks like.

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?

The tool takes zero parameters, so there is nothing for the schema to document and no gap for the description to compensate for. The mention of city_id refers to a downstream call, not an input here, and is correctly framed as such.

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?

States a specific verb and resource: "List Klook countries and destination areas," then narrows to "bookable country list" and "destination-guide area tree." That is clearly distinct from attraction-search siblings, though it never names an alternative tool to disambiguate against.

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?

Gives forward guidance — "Use a city_id with /klook/search to browse that destination" — which tells the agent what to do with the result. It does not say when to prefer this over klook_attractions_destinations or klook_categories, nor state any exclusion, so usage is implied rather than codified.

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

Deploy Server

Other Tools