Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

klook_verticals

Read-only

List Klook's complete navigation vertical menu (Things to do, WiFi & SIM Card, Transportation, Train Tickets & Passes, Food & Dining) with each vertical's type key, display name, icon and absolute URL, including nested children such as Attractions & Shows and Tours & Sightseeing. Takes no input. Use it to discover which Klook product verticals exist and where each one lives before choosing a vertical-specific tool; klook_hot returns the curated popular-destination and popular-activity lists 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_verticals"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

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

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

The annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds useful behavior: it takes no input, returns the complete navigation menu, includes icon and absolute URL data, and includes nested children. It does not discuss ordering or other operational details, but those gaps are minor for a discovery tool.

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 definition is front-loaded around the core action and scope, then adds examples and routing guidance. The parenthetical vertical list is long but useful for recognition. Every sentence contributes either scope, return detail, or alternative-tool guidance.

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 zero-input discovery tool with annotations and an output schema, the description is complete enough. It covers what is listed, what fields are included, that nested children are included, that no input is required, and when to use it versus klook_hot.

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?

There are zero parameters, so the baseline is 4. The description explicitly says 'Takes no input,' which removes any ambiguity. No further parameter semantics are needed.

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: it lists Klook's complete navigation vertical menu. It names the returned fields and nested children, and it explicitly distinguishes this tool from klook_hot. An agent can identify its purpose without opening the 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 explicit when-to-use guidance: discover which product verticals exist and where each lives before choosing a vertical-specific tool. It also names the alternative klook_hot and explains that klook_hot returns curated popular-destination and popular-activity lists instead.

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