Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

klook_suggest

Autocomplete Klook activities, cities, and countries from partial queries; returns matching IDs for search and activity lookup.

Instructions

Autocomplete Klook activities, cities and countries. Returns Klook autocomplete matches for a partial query: matching activities, destination cities with city ids, and countries. Use a returned city_id with /klook/search, or an activity_id with /klook/activities/{activity_id}.

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_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.5/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden; it does disclose the three result categories and that city matches carry ids, which is meaningful return-shape information. It omits anything about match ordering, minimum partial-query behavior, whether activities are truncated while cities/countries are not, and any auth or rate-limit constraints for the underlying Klook API.

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 the core action and return contents, then the follow-up routing instruction. No filler, though the second sentence's itemized list slightly restates the first.

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?

A two-parameter read-only autocomplete with no output schema, so the description is correct to describe the returned match categories, which it does. The remaining gaps are how the 'limit' interacts with non-activity results and whether empty/no-match responses are possible, both minor for a suggest endpoint.

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 coverage is 100%, so both parameters are already documented, establishing a baseline of 3. The description adds only the notion of a 'partial query'; it never addresses the 'limit' parameter or clarifies that the limit applies specifically to activities, leaving a real ambiguity about result truncation unaddressed.

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 opens with a specific verb+resource pair ('Autocomplete Klook activities, cities and countries') and then enumerates exactly what kinds of entities come back. It does not name a sibling tool for contrast, though the reference to '/klook/search' implies the split between suggesting and searching.

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 tells the agent what to do with results (city_id -> /klook/search, activity_id -> /klook/activities/{activity_id}), which is useful downstream routing. It does not state when to prefer this over klook_search, klook_attractions_suggest, or other suggest tools, so the choice among lookalike siblings 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.

Deploy Server

Other Tools