Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

klook_destinations

Read-only

List Klook's bookable countries and destination-guide regions: each country's id, display name and ISO country code, plus every region's areas with city_id, country_id, name and listing URL, together with country and area counts. Takes no input. This is the discovery step for klook_search's city_id parameter, so pick a city from the area tree instead of guessing an id. Use klook_categories for category ids or klook_suggest to resolve a place or activity name quickly.

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

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds that the call 'takes no input' and that the response is a full country/area tree with counts, which tells the agent this is a single static catalog read rather than a paginated or filtered query. It stops short of noting data freshness or any rate-limit behavior, so it is not exhaustive.

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?

Three sentences, front-loaded with purpose and ending with sibling routing; nothing is filler. The first sentence is somewhat long and re-enumerates return fields that the output schema already documents, which is the only mild redundancy.

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?

For a zero-parameter, read-only catalog tool with an output schema and readOnly/openWorld annotations, the description covers purpose, workflow position, and alternatives. There is nothing an agent needs in order to select and invoke this correctly that is missing.

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 the baseline of 4 applies. The description reinforces this explicitly with 'Takes no input,' leaving no ambiguity that filtering must happen elsewhere (via klook_search's city_id).

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 opens with a specific verb plus resource ('List Klook's bookable countries and destination-guide regions') and then enumerates exactly what each record carries (country id, display name, ISO code; area city_id, country_id, name, listing URL, plus counts). An agent can distinguish this catalog-listing tool from klook_search or klook_categories 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 Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states the exact role in the workflow ('the discovery step for klook_search's city_id parameter') and gives an explicit anti-pattern ('pick a city from the area tree instead of guessing an id'). It also routes to two named alternatives with their distinct purposes (klook_categories for category ids, klook_suggest for name resolution).

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

All Crawlora MCP toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources