独行录 / opcmenu

确认后发布组织提案活动

create_organization_proposal_activity

【需要登录】【对外发布】先 preview=true，向用户逐项展示活动全文、时间、地点、闭门受众与受邀名单；用户确认后带 previewHash 和同一份 activity/signup/excludeUserIds，preview=false 发布。activity 复用正式活动 schema，线下必须有地点；signup 仅托管报名，默认平台表单。受邀人重新从当前可见提案取，不能注入别的人；云用户发布后另邀。默认不推送，notifyInvitees=true 才通知真人。发布时同事务把提案记为 CONVERTED 并关联活动，不能用通用草稿发布代替。已转换的提案返回现有活动，避免再次创建；任何预览变化都要再确认。

Input Schema

TableJSON Schema

Name	Required	Description
`signup`	No
`preview`	No	默认 true 仅预览；用户确认后才传 false 执行
`activity`	Yes
`proposalId`	Yes	list_organization_proposals 返回的提案 id
`previewHash`	No	执行时必须传最新预览的 previewHash；参与人或内容有变化会要求重新确认
`appActivation`	No
`excludeUserIds`	No
`notifyInvitees`	No
`organizationId`	Yes	组织或联盟空间的组织 id

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 14, 2026

addedInput schema / properties / activity / properties / venueId

Added value: +{
+  "anyOf": [
+    {
+      "anyOf": [
+        {
+          "not": {}
+        },
+        {
+          "maxLength": 64,
+          "minLength": 1,
+          "type": "string"
+        }
+      ]
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

Changed3 schema fields changedOct 8, 2026

addedInput schema / properties / activity / properties / allowAnnualPassUpgrade
```
Added value: +{
+  "const": false,
+  "type": "boolean"
+}
```

addedInput schema / properties / activity / properties / annualPassPriceCents

Added value: +{
+  "anyOf": [
+    {
+      "anyOf": [
+        {
+          "not": {}
+        },
+        {
+          "maximum": 100000000,
+          "minimum": 1,
+          "type": "integer"
+        }
+      ]
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

addedInput schema / properties / activity / properties / priceCents

Added value: +{
+  "maximum": 100000000,
+  "minimum": 0,
+  "type": "integer"
+}

Changed1 schema field changedOct 5, 2026
- addedInput schema / properties / activity / properties / memberMatchingEnabled
```
Added value: +{
+  "type": "boolean"
+}
```
Changed1 schema field changedOct 4, 2026
- changedInput schema / properties / excludeUserIds / maxItems
```
Previous value: -60New value: +100
```
AddedOct 4, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Adds substantial context beyond the annotations: it discloses the preview/confirmation gate, that invitees are re-fetched from the current visible proposal and cannot be injected, that cloud users are invited separately, that notifications default off unless notifyInvitees=true, and that publishing marks the proposal CONVERTED in the same transaction. It also clarifies handling of already-converted proposals, which is behavioral detail not present in the structured fields.

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 description is long, but it is front-loaded with the core preview-then-publish workflow and every sentence carries operational information. The run-on paragraph structure is dense rather than wasteful, though it could be easier to scan if broken into shorter chunks.

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 complex mutation with nested activity and signup objects, no output schema, and broad annotation coverage, the description supplies the missing operational contract: preview hash validation, invitee sourcing, notification defaults, transaction behavior, and repeat-conversion handling. An agent has enough context to call it correctly without further explanation.

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 description coverage is only 44%, so the description must compensate, and it does so for key parameters: preview, previewHash, activity, signup, excludeUserIds, and notifyInvitees all receive meaningful usage context. It does not explain every nested field or appActivation, so it stops short of full semantic coverage.

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?

Names a specific verb and resource: publish an organization proposal activity after confirmation. It explicitly distinguishes itself from generic draft publishing and from recreating an already-converted proposal, so an agent can route correctly among siblings such as publish_activity_draft or create_organizer_activity.

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?

Gives an explicit two-stage workflow: first call with preview=true, show the user the full activity, time, location, closed audience, and invitees, then call with preview=false using previewHash after confirmation. It also states when not to use it by warning that generic draft publishing is not an acceptable substitute.

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

All 独行录 / opcmenu tools Inspect

Try in Browser

Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?