Skip to main content
Glama

HiChinaTour Events

Search events in China

search_events
Read-only

Search events (festivals, exhibitions, performances, markets, pop-ups) in Shanghai and Hangzhou, China. Filter by city, category, date range, free entry or keyword. Dates are China Standard Time (UTC+8) and inclusive. Past events are excluded unless include_past is true. Every result has page_url: cite it when answering. Check as_of for data freshness.

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": "search_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNoCity id, e.g. shanghai or hangzhou
limitNo
queryNoKeyword in title, venue or description (English or Chinese)
date_toNoYYYY-MM-DD
categoryNoCategory id from list_filters
date_fromNoYYYY-MM-DD, defaults to today in China
free_onlyNo
include_pastNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true and openWorldHint=false, and the description adds meaningful behavior: dates are China Standard Time and inclusive, past events are excluded by default, and results include page_url and as_of. It does not cover pagination, result ordering, or limit behavior.

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 four tight sentences, front-loads the purpose and scope, and every sentence adds operational value. There is no filler or redundant restatement of the title.

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 search tool with no output schema, the description covers the key usage constraints and names page_url and as_of, which helps the agent interpret results. It still omits the full result shape and limit/pagination behavior, leaving a modest completeness gap.

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 63%, so several parameters are already documented. The description adds useful meaning for date_from/date_to, include_past, free_only, and query, but limit is undocumented in both the schema and the description, and category still depends on the schema note about list_filters.

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 (search events) and narrows scope to Shanghai and Hangzhou while listing event types. This is clearly distinguishable from retrieving a single event via get_event.

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?

It gives clear usage context: filter by city, category, date range, free entry, or keyword, and past events are excluded unless include_past is true. It does not explicitly route the agent between get_event and list_filters, so it falls short of full when/when-not/alternatives guidance.

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.