Skip to main content
Glama
Sign In

cuqu-mcp

by net.cuqu.agent
OverviewDiscussionsAdmin

query_activities

查询粗趣小程序上的活动列表。

当用户想找活动、看有什么活动、按条件筛选活动时调用此工具。

Args:
    activity_type: 活动类型筛选，如"桌游聚会"、"户外徒步"、"剧本杀"、"飞盘"等。留空则不筛选。
    date: 日期筛选，格式"2026-08-22"。留空则不筛选。
    location: 区域筛选，如"南山区"、"罗湖区"。留空则不筛选。
    keyword: 关键词搜索活动标题和描述。留空则不搜索。

Returns:
    JSON 字符串，包含活动列表（标题、时间、地点、价格、剩余名额、H5 链接等）

Input Schema

NameRequiredDescriptionDefault
dateNo日期筛选。支持「今天/明天/周末/本周」「2026-11-01」等自然语言与标准日期，不传表示不限日期
limitNo返回条数上限，1-100，默认 50。想看更多就传大一点
keywordNo关键词，在活动标题与描述中模糊匹配，如：露营、新手、女生场。不传表示不过滤
districtNo区/县名，如：南山、福田、龙岗、惠东县。与 location 同传时按 城市+区 两级过滤。不传则不过滤区
locationNo城市名，如：深圳、广州、惠州、东莞。不传表示不限城市
activity_typeNo活动类型，如：桌游聚会、徒步、飞盘、羽毛球、二次元、钓鱼。模糊词请传完整常见说法（如「桌游聚会」而非「桌游」），传错会返回空

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • addedInput schema / properties / activity_type / description
      Added value: +"活动类型，如：桌游聚会、徒步、飞盘、羽毛球、二次元、钓鱼。模糊词请传完整常见说法（如「桌游聚会」而非「桌游」），传错会返回空"
    • addedInput schema / properties / date / description
      Added value: +"日期筛选。支持「今天/明天/周末/本周」「2026-11-01」等自然语言与标准日期，不传表示不限日期"
    • addedInput schema / properties / district
      Added value: +{
+  "description": "区/县名，如：南山、福田、龙岗、惠东县。与 location 同传时按 城市+区 两级过滤。不传则不过滤区",
+  "type": "string"
+}
    • addedInput schema / properties / keyword / description
      Added value: +"关键词，在活动标题与描述中模糊匹配，如：露营、新手、女生场。不传表示不过滤"
    • addedInput schema / properties / limit
      Added value: +{
+  "description": "返回条数上限，1-100，默认 50。想看更多就传大一点",
+  "type": "integer"
+}
    • addedInput schema / properties / location / description
      Added value: +"城市名，如：深圳、广州、惠州、东莞。不传表示不限城市"
  2. Changed2 schema fields changed
    • removedInput schema / properties / district
      Removed value: -{
-  "description": "区/县名，如：南山、福田、龙岗、惠东县。与 city 同传时按 城市+区 两级过滤；支持常见别名（area/zone）。不传则不过滤区",
-  "type": "string"
-}
    • removedInput schema / properties / limit
      Removed value: -{
-  "description": "返回条数上限，1-100，默认 50。想看更多就传大一点",
-  "type": "integer"
-}
  3. Changed2 schema fields changed
    • addedInput schema / properties / district
      Added value: +{
+  "description": "区/县名，如：南山、福田、龙岗、惠东县。与 city 同传时按 城市+区 两级过滤；支持常见别名（area/zone）。不传则不过滤区",
+  "type": "string"
+}
    • addedInput schema / properties / limit
      Added value: +{
+  "description": "返回条数上限，1-100，默认 50。想看更多就传大一点",
+  "type": "integer"
+}
  4. First observed

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It does disclose the return shape (title, time, location, price, remaining slots, H5 link), which is useful, but it never states that this is a pure read operation, whether results are paginated/capped, or what happens when filters yield nothing — and the sibling get_activity_card hints that single-activity retrieval is a separate concern this tool does not cover.

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?

Well front-loaded: purpose, then when-to-use, then parameters, then returns. The Args block largely restates schema fields that already have 100% description coverage, so it is somewhat redundant, but the ordering makes it easy to scan and no sentence is pure filler.

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 read-only, zero-required-parameter query tool this covers purpose, invocation triggers, most filters, and return content. The gaps are minor given the schema and output schema exist: no mention of `limit`/result caps or of what an empty result set looks like, and the location-vs-district semantics conflict with the schema.

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 coverage is 100% so the baseline is 3, and the schema is actually richer than the description in key ways. The description omits the `limit` and `district` parameters entirely, and its `location` entry describes a district-level filter with examples like 南山区/罗湖区, whereas the schema defines `location` as a city (深圳/广州) and puts districts in `district` — a mismatch that could steer an agent to pass a district name to the wrong parameter. It also narrows `date` to the "2026-08-22" format while the schema supports 今天/明天/周末.

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 opening line states a specific verb and resource (query the activity list on the Cuqu mini-program), which is clearly distinct from write-oriented siblings like create_activity and register_event. It does not explicitly contrast itself with get_activity_card (single activity) or query_venues (venues), so differentiation is inferable but not spelled out.

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?

The second line gives an explicit trigger condition: call this when the user wants to find activities, browse what's available, or filter by conditions. That covers the primary use cases well, but it names no exclusions or alternative tools for overlapping needs (e.g. fetching a single activity's detail).

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

All cuqu-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