Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

klook_attractions_destinations

Discover Klook attraction destinations and retrieve hot countries with activity cards, plus hot cities by country ID or nearby cities by city ID.

Instructions

Discover Klook attractions destinations. Returns Klook's attractions destination-discovery surface: the hot attractions countries with their top activity cards (always), the hot cities for a country (when country_id is supplied), and the cities near a destination city (when city_id is supplied). Note the two country id spaces: the response's countries[].country_id uses Klook's activity-country ids (Japan is 1012), while the country_id parameter uses the destination-country ids from /klook/destinations (Japan is 12) because that is what Klook's hot-city read accepts. Nearby cities carry their upstream distance in kilometres; hot cities do not. Empty hot-city or nearby-city lists are valid answers.

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_attractions_destinations"
  }
}

Input Schema

NameRequiredDescriptionDefault
city_idNoKlook city id; adds nearby cities and scopes the hot-city list
country_idNoKlook destination-country id from /klook/destinations; adds the hot-city list

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full load and delivers genuinely non-obvious behavior: the two distinct country id spaces (activity-country ids in the response vs destination-country ids in the parameter), that nearby cities carry upstream distance while hot cities do not, and that empty hot-city/nearby-city lists are valid rather than an error. It omits pagination, result caps, and auth/rate-limit context.

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 outcome (what the surface returns) before the conditional details, and every sentence carries information — the id-space note and the distance caveat both prevent real misuse. The single dense paragraph with parenthetical clauses is harder to scan than it needs to be, which keeps it from a 5.

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?

There is no output schema, so the description must describe the return shape, and it does — naming the countries[] cards, the country-scoped hot cities, and nearby cities with distances. For a zero-required-parameter discovery tool this is nearly sufficient; only volume/pagination expectations are unstated.

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 100%, so a 3 is the baseline, but the description adds real meaning beyond the schema: it explains that country_id must come from /klook/destinations and is NOT the same id space as the country_id surfaced in the response, and that city_id both adds nearby cities and re-scopes the hot-city list. That id-space warning is the kind of thing the schema alone cannot convey.

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 ('Discover Klook attractions destinations') and enumerates the three payloads the tool returns: hot countries with top activity cards, hot cities for a country, and nearby cities. It implicitly separates itself from klook_destinations by naming that route as the id source, but it never explicitly contrasts its role with the sibling's, so it stops short of a 5.

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?

Usage is expressed through parameter-triggered conditions: country_id 'adds the hot-city list', city_id 'adds nearby cities and scopes the hot-city list', and with neither param the tool still returns hot countries. That gives an agent clear call-shaping guidance. It lacks explicit when-not-to-use or named alternative tools, which keeps it below 5.

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