Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

klook_recommendations

Retrieve Klook’s curated category recommendations for a destination or global default, returning named sections with activity cards and call-to-action buttons to support trip planning.

Instructions

Get Klook curated category recommendations. Returns Klook's curated "unmissable experiences" sections for a destination (or its default global selection): named category sections with their activity cards, plus the call-to-action button. Use city_id from /klook/destinations or /klook/suggest to scope the sections; use /klook/search or /klook/attractions/search for a full result page instead.

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

Input Schema

NameRequiredDescriptionDefault
city_idNoKlook city id to scope the curated sections to

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A4.7/5.0
Behavior4/5

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

No annotations were supplied, so the description carries the full burden; it discloses the fallback behavior when city_id is omitted (default global selection) and enumerates the returned payload structure, which matters because there is no output schema. It does not mention pagination, rate limits, auth requirements, or caching, which leaves some behavioral gaps for a fully unannotated tool.

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?

Two sentences, front-loaded with the purpose and payload, then the sourcing and alternative-tool guidance. Every clause carries actionable information and nothing is repeated from structured fields verbatim.

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 single-optional-parameter, unannotated read tool with no output schema, the description covers purpose, payload shape, parameter sourcing, default behavior, and sibling alternatives. Nothing an agent needs in order to invoke it correctly 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?

Schema coverage is 100% and there is only one optional parameter, so the baseline would be 3. The description earns a point above baseline by adding provenance ('use city_id from /klook/destinations or /klook/suggest') and by explaining the consequence of omitting it, neither of which the schema states.

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?

States a specific verb and resource ('Get Klook curated category recommendations') and explains exactly what the response contains: named category sections, activity cards, and the call-to-action button. It also distinguishes itself from sibling tools by naming /klook/search and /klook/attractions/search as the route for a full result page, so an agent can select correctly 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?

Gives explicit when-to-use ('curated sections for a destination'), when-not ('use search for a full result page instead'), and where the city_id value comes from (/klook/destinations or /klook/suggest). The only mild omission is that the no-city_id case is described as a 'default global selection' rather than stated as explicitly optional, but the guidance is otherwise complete.

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