CUQU找搭子 (CUQU) MCP Server

create_activity

主理人在粗趣小程序上发布新活动。

当用户（主理人）想创建/发布一个活动时调用此工具。

Args:
    title: 活动标题，如"周六桌游聚会"
    activity_type: 活动类型，如"桌游聚会"、"户外徒步"、"剧本杀/密室"等
    date: 活动日期，格式"2026-08-22"
    time: 活动时间段，如"14:00-18:00"
    location: 活动地点，如"南山区·科兴科学园"
    max_participants: 最大参与人数，数字字符串或整数均可，如 "15" 或 15
    price: 人均费用（元），数字字符串或整数均可，如 "39" 或 39，免费填 "0" 或 0
    description: 活动描述和注意事项
    organizer: 主理人名称

Returns:
    JSON 字符串，包含活动 ID 和详情链接

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": {
      "title": "<title>",
      "activity_type": "<activity_type>",
      "date": "<date>",
      "time": "<time>",
      "location": "<location>"
    },
    "name": "create_activity"
  }
}

Input Schema

Name	Required	Description	Default
`date`	Yes	活动日期，格式 YYYY-MM-DD
`time`	Yes	开始时间，格式 HH:MM，如 19:30
`price`	No	单人价格（元），免费填 0	0
`title`	Yes	活动标题，一句话说清是什么活动，如「周六南山羽毛球新手局」
`location`	Yes	活动地点，尽量写到区或具体场馆
`organizer`	No	主理人（组织者）称呼或昵称
`description`	No	活动详细介绍，包括流程、适合谁、需要带什么
`activity_type`	Yes	活动类型，如：桌游聚会、徒步、飞盘、羽毛球
`max_participants`	No	人数上限（整数）	0

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed9 schema fields changedOct 29, 2026

addedInput schema / properties / activity_type / description

Added value: +"活动类型，如：桌游聚会、徒步、飞盘、羽毛球"

addedInput schema / properties / date / description

Added value: +"活动日期，格式 YYYY-MM-DD"

addedInput schema / properties / description / description

Added value: +"活动详细介绍，包括流程、适合谁、需要带什么"

addedInput schema / properties / location / description

Added value: +"活动地点，尽量写到区或具体场馆"

addedInput schema / properties / max_participants / description
```
Added value: +"人数上限（整数）"
```

addedInput schema / properties / organizer / description

Added value: +"主理人（组织者）称呼或昵称"

addedInput schema / properties / price / description

Added value: +"单人价格（元），免费填 0"

addedInput schema / properties / time / description

Added value: +"开始时间，格式 HH:MM，如 19:30"

addedInput schema / properties / title / description

Added value: +"活动标题，一句话说清是什么活动，如「周六南山羽毛球新手局」"

First observedSep 28, 2026

TDQS

A3.5/5.0

Behavior3/5

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

No annotations are provided, so the description must carry the full behavioral burden. It discloses that the result is a JSON string with an activity ID and a detail link, which is useful; however, it says nothing about whether publishing is immediate or visible to others, who is authorized, or how duplicates are handled.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded in one clear sentence, but the Args block repeats schema descriptions nearly verbatim, so it costs space without adding information. This is acceptable but not tight.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Because an output schema exists, the return-value explanation is not strictly necessary. However, for a 9-parameter mutation tool with no annotations, the description leaves out authorization and visibility behavior, which is a meaningful gap.

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 schema already documents all 9 parameters, making 3 the baseline. The Args section largely restates the schema, and its example for time ('14:00-18:00') is a range, while the schema defines time as a start time ('HH:MM'), which adds mild ambiguity rather than clarity.

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?

States a specific verb and resource in a specific platform context ('主理人在粗趣小程序上发布新活动'), which is unambiguous. It does not name or differentiate itself from siblings like query_activities or register_event, so it stops short of a 5.

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?

'当用户（主理人）想创建/发布一个活动时调用此工具' gives a clear trigger condition and an actor (主理人). There are no exclusions or named alternatives, such as when to use query or register instead.

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

All CUQU找搭子 (CUQU) MCP Server tools Inspect

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.