Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

klook_attractions_highlights

Read-only

Return Klook's attractions highlight sections for a destination: named groups (for example Bestsellers) with their activity cards, plus the group's call-to-action button. Provide city_id or country_id (at least one is required) and optionally type city or country to choose the scope; the default follows whichever id you supply. Use it for a curated shortlist, then klook_attractions_search for the full listing or klook_activity for one card.

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

Input Schema

NameRequiredDescriptionDefault
typeNoHighlight scope: city or country. Defaults to city when city_id is set, country otherwise.
city_idNoKlook city id. Required when country_id is not set.
country_idNoKlook country id. Required when city_id is not set.

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

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

The annotations already declare this as a read-only, open-world operation. The description adds useful behavioral context by explaining that it returns grouped highlight sections with cards and a call-to-action button. It does not discuss pagination, ordering, or rate limits, but the output schema and annotations cover much of that ground.

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?

The description is front-loaded with the return value, then the parameter requirement, then the usage routing. Three sentences carry purpose, inputs, and alternatives without wasted wording. The parenthetical Bestsellers example is helpful rather than bloated.

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 read-only discovery tool with full schema coverage, annotations, and an output schema, the description is complete. It covers what is returned, the required id constraint, scope selection, and sibling alternatives. Nothing material needed 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.

Parameters3/5

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

Schema description coverage is 100%, so the meaning of city_id, country_id, and type is already well documented. The description restates the at-least-one-id requirement and default scope behavior, but adds little beyond the schema. A baseline 3 is appropriate.

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 states a specific verb and resource: return Klook attractions highlight sections for a destination. It explains the content precisely, naming groups such as Bestsellers, activity cards, and a call-to-action button. It also distinguishes this tool from klook_attractions_search and klook_activity.

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 explicitly says to use this tool for a curated shortlist and directs the agent to klook_attractions_search for the full listing or klook_activity for one card. It also states the required id condition and the optional scope parameter, leaving little ambiguity about when and how to call it.

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