Skip to main content
Glama

Search venues

search_venues
Read-onlyIdempotent

Search verified Common Room venues in Hong Kong by type, with optional district, date, number of people and budget. Types offered: hourly_hotel = Hourly hotels / 時鐘酒店; party_room = Party Rooms in Hong Kong / Party Room 香港; event_venue = Event Venue Hong Kong / 場地租用 (商業) 香港; restaurant_private_room = Private Room Restaurant Hong Kong / 包房餐廳 / 餐廳包場; junk_boat = Boat Party / Junk Hong Kong / 船p / 遊船河 租船; serviced_apartment = Serviced Apartment in Hong Kong / Service Apartment Hong Kong (服務式住宅香港) 月租/短租. For serviced_apartment it returns only the category page link; do not recommend apartments.

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": {
      "type": "<type>"
    },
    "name": "search_venues"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoDate as YYYY-MM-DD (Hong Kong time). For hourly hotels, only hotels with open times that day are returned.
typeYesThe type of place.
limitNoMaximum results (default 8).
budgetNoMaximum starting price in HKD, as shown on the listing.
peopleNoNumber of people.
districtNoHong Kong district in English or Chinese, such as "Mong Kok" or "旺角".
languageNoResult language: "zh" (default) or "en".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

The annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so the safety profile is covered. The description adds real behavioral context beyond them: results are 'verified' venues, and one type silently degrades to a category link rather than listings — a caveat an agent would otherwise miss. Remaining gaps are ordering/pagination and empty-result behavior, which are minor for a read-only search.

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 search scope is front-loaded in the first sentence, followed by the type vocabulary and the serviced_apartment caveat at the end. The type list is long but each bilingual alias carries matching value; the only cost is that the second sentence becomes a single dense run-on block that is harder to scan than a list.

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 7-parameter read-only search with full schema coverage and no output schema, the description covers purpose, filters, the type domain and the one degraded return mode. Ordering of results, default limit, and whether multiple filters combine as AND are left to the schema or unstated, which is a modest gap rather than a blocker.

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?

Schema coverage is 100%, so the schema already documents every parameter and the baseline would be 3. The description earns more by translating the opaque enum slugs into real-world concepts with Chinese and English synonyms (e.g. junk_boat = 船p / 遊船河 租船), which lets an agent map colloquial user queries to the correct enum value — meaning the schema alone cannot convey.

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 uses a specific verb and resource ('Search verified Common Room venues in Hong Kong') and scopes it to the supported filter set, so an agent immediately knows what the tool returns. It stops short of naming or contrasting with the siblings check_availability and get_venue_details, leaving the routing to the agent's inference from tool names.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage context is explicit: search by type with optional district/date/people/budget narrowers, plus the unusual but important rule that serviced_apartment returns only a category page link and apartments should not be recommended. What is missing is any statement of when to call this versus check_availability or get_venue_details.

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.

Resources