Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

klook_recommendations

Read-only

Return Klook's curated 'unmissable experiences' category sections for a destination, or its default global selection when city_id is omitted: each section's title, icon, tint, see-more URL and its activity cards, plus the overall title and call-to-action button. Use it for a curated shortlist; use klook_search or klook_attractions_search for a full paginated result page, klook_hot for popular destinations/activities, and klook_search_filters when you need the filter value spaces.

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_idNoOptional Klook city id to scope the curated category sections to.

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 safety is covered. The description adds genuinely new behavior: omitting city_id silently falls back to a default global selection, which is a non-obvious result-shaping rule an agent must know. It stops short of covering rate limits, auth, or caching, so a 4 rather than 5.

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 purpose and followed by the routing guidance. The enumeration of returned fields (title, icon, tint, see-more URL, cards, CTA) is somewhat redundant given an output schema exists, but it is compact and not padded with filler.

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?

With a single optional parameter, full schema coverage, an output schema, and read-only annotations, the description supplies everything an agent needs: what comes back, what happens with no argument, and which sibling to pick instead. No material gap remains for this tool's complexity.

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 the single city_id parameter is already documented and the baseline is 3. The description goes beyond it by explaining the consequence of omission — the tool returns a default global selection rather than erroring or returning nothing — which is semantic information the schema does not convey.

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 — returning Klook's curated 'unmissable experiences' category sections for a destination, or the default global selection when city_id is omitted — and enumerates what each section carries. This is clearly distinguishable from klook_search and klook_attractions_search, which are named as the paginated alternatives.

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?

Explicitly says to use it for a curated shortlist, and names three alternatives with the condition that selects each: klook_search/klook_attractions_search for a full paginated result page, klook_hot for popular destinations/activities, klook_search_filters for filter value spaces. Nothing is left to inference.

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