Skip to main content
Glama

klook_attractions_suggest

Read-only

Return Klook attractions autocomplete matches for a partial name: matching attraction activities with ids, canonical URLs, city id and name, category id and image, plus matching cities and countries. query is required and must be 2 to 80 characters; limit caps returned activities from 1 to 20 and defaults to 10. Use it when you need an attraction id or city id from a name, then pass the activity_id to klook_activity or the city_id to klook_attractions_search; klook_suggest covers tours and experiences 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_attractions_suggest"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum activities to return, 1-20. Defaults to 10.
queryNoText to complete. Required, 2-80 characters.

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.3/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 largely covered. The description still adds useful behavioral detail: the tool returns three distinct match families (activities, cities, countries) and supplies ids/URLs/images rather than free text, which tells the agent this is an id-resolution step, not a browsing call. It stops short of mentioning ordering, fuzzy-match behavior, or pagination beyond the limit cap.

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 tightly packed sentences: what is returned, the input constraints, then the routing/alternative guidance, in that order. Nothing is padded, though the mid-sentence field enumeration is dense enough to be slightly harder to scan than the front-loaded purpose statement.

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?

With an output schema present, the description does not need to document return payloads, and it correctly avoids doing so while still summarising the match families. Combined with the explicit id-handoff routing, an agent has what it needs to call this correctly; only match-quality/ordering behavior is left unstated.

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 parameters are already documented. The description largely restates the same constraints (query required 2-80 chars, limit 1-20 defaulting to 10), adding only the nuance that limit caps returned activities specifically rather than cities/countries. That is a marginal gain over the schema, so the baseline of 3 applies.

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+resource ("Return Klook attractions autocomplete matches for a partial name") and then enumerates exactly what is matched: activities with ids/URLs/city/category, plus cities and countries. It also distinguishes itself from the sibling klook_suggest, which covers tours and experiences, so an agent can pick correctly without opening a 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 gives an explicit trigger ("Use it when you need an attraction id or city id from a name") and explicit downstream routing (activity_id to klook_activity, city_id to klook_attractions_search). It also names the alternative for a different intent, klook_suggest for tours and experiences, which is exactly the when-not guidance the dimension asks for.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.