Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

klook_attractions_suggest

Autocompletes Klook attractions, cities, and countries from a partial query, returning matching activity IDs, city IDs, images, and URLs for ticket and destination lookup.

Instructions

Autocomplete Klook attractions, cities and countries. Returns Klook attractions-vertical autocomplete matches for a partial query: matching attraction tickets with ids, city ids, images and URLs, plus matching destination cities and countries. Use a returned activity_id with /klook/activities/{activity_id} or its city_id with /klook/attractions/search.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "klook_attractions_suggest"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum activities to return, 1-20
queryYesText to complete, 2-80 characters

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and does well: it states that the tool returns autocomplete matches including IDs, images, and URLs. It does not mention auth, rate limits, or explicitly confirm read-only behavior, but for an autocomplete tool the described behavior is fairly complete.

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?

The definition is front-loaded and appropriately short, with the core purpose in the first sentence and return details after it. The phrase 'Klook attractions-vertical autocomplete matches' is slightly redundant, but the downstream ID guidance earns its place.

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 simple two-parameter suggest tool with no annotations or output schema, the description provides enough information about inputs, returned match types, and how to use returned IDs. The main missing piece is explicit comparison to sibling suggest and search tools.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so both query and limit are already documented in structured fields. The description adds only mild context by calling the query a partial query and clarifying that results include attractions plus destination cities and countries; it does not add syntax or constraints beyond the schema.

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?

The description states a specific verb and resource: autocomplete Klook attractions, cities, and countries. It also scopes the tool to the attractions vertical, which helps distinguish it from generic suggest/search tools, though it does not explicitly name sibling alternatives.

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?

It implies the tool is for partial queries and explains how to use returned activity_id and city_id values downstream. However, it does not explicitly say when to use this instead of klook_suggest, klook_attractions_search, or klook_search_unified, nor does it state when not to use it.

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