独行录 / opcmenu

保存合作方案

save_cooperation_plan

Destructive

新增或编辑本人合作方案。新建时让用户明确purpose为GENERAL通用或TARGETED专属（targetUserId），缺省LEGACY不可新发送。旧稿/切用途先用Agent ADAPT_PURPOSE整理，再请用户预览确认；不得只修改用途标签。默认 PRIVATE+DRAFT。只有GENERAL且用户明确同意才能设 PUBLIC；PUBLISHED表示完整可发送，PRIVATE+PUBLISHED仍只可定向发送。发布需要标题、摘要、背景、理想合作方、合作方式和对方收益完整。正文默认纯文本；用户需要表格、小标题、列表时可设 contentFormat=markdown（支持 #~### 标题、粗体、- / 1. 列表、> 引用、| 表格、--- 分隔线，不支持图片与 HTML），老版本 App 显示原文。sectionTitles 可按节覆盖展示标题（每个≤20字，缺省用固定标题）。

Input Schema

TableJSON Schema

Name	Required	Description	Default
`id`	No
`plan`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 26, 2026

addedInput schema / properties / plan / properties / contentFormat

Added value: +{
+  "default": "plain",
+  "enum": [
+    "plain",
+    "markdown"
+  ],
+  "type": "string"
+}

addedInput schema / properties / plan / properties / sectionTitles

Added value: +{
+  "additionalProperties": false,
+  "default": {},
+  "properties": {
+    "advantages": {
+      "$ref": "#/properties/plan/properties/sectionTitles/properties/description"
+    },
+    "cooperationModes": {
+      "$ref": "#/properties/plan/properties/sectionTitles/properties/description"
+    },
+    "description": {
+      "type": "string"
+    },
+    "nextSteps": {
+      "$ref": "#/properties/plan/properties/sectionTitles/properties/description"
+    },
+    "partnerBenefits": {
+      "$ref": "#/properties/plan/properties/sectionTitles/properties/description"
+    },
+    "partnerProfile": {
+      "$ref": "#/properties/plan/properties/sectionTitles/properties/description"
+    }
+  },
+  "type": "object"
+}

Changed4 schema fields changedSep 19, 2026

addedInput schema / properties / plan / properties / expectedUpdatedAt
```
Added value: +{
+  "format": "date-time",
+  "type": "string"
+}
```

addedInput schema / properties / plan / properties / purpose

Added value: +{
+  "default": "LEGACY",
+  "enum": [
+    "GENERAL",
+    "TARGETED",
+    "LEGACY"
+  ],
+  "type": "string"
+}

addedInput schema / properties / plan / properties / purposeReviewConfirmed
```
Added value: +{
+  "type": "boolean"
+}
```

addedInput schema / properties / plan / properties / targetUserId

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

AddedSep 19, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations already indicate a destructive write operation, and the description adds substantial behavioral context: default PRIVATE+DRAFT, the PUBLIC-only-for-GENERAL-with-consent rule, PUBLISHED semantics, required fields for publishing, markdown support limitations, old-app rendering behavior, and sectionTitles constraints. This goes well beyond the annotation hints.

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 dense and every sentence carries meaningful constraints or workflow rules. It is front-loaded with the core create/edit purpose. However, it is a long unbroken block of text; structuring it into workflow rules and parameter semantics would improve scannability without losing content.

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?

Given the complex nested schema, no output schema, and minimal annotations, the description covers many important defaults, constraints, and edge cases. The main gap is the missing explanation of how id selects create vs edit, plus a few lesser-used fields that remain undocumented. Overall it is strong but not exhaustive.

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 0%, so the description must compensate. It does explain key parameters: purpose (GENERAL/TARGETED/LEGACY), targetUserId, visibility, status, contentFormat, and sectionTitles. However, it does not clarify the id parameter's role in distinguishing create vs edit, nor does it cover fields like references, importId, expectedUpdatedAt, or purposeReviewConfirmed.

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 states the verb and resource clearly: '新增或编辑本人合作方案' (create or edit own cooperation plan). It is specific about the object and action, but it does not explicitly differentiate itself from the sibling tool edit_cooperation_plan_with_agent, leaving some potential ambiguity about which write path to choose.

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?

The description gives explicit usage context: new plans must clarify purpose, old drafts or purpose changes must first go through Agent ADAPT_PURPOSE and user preview confirmation, and it warns against only modifying the purpose label. It also specifies when PUBLISHED/PUBLIC is allowed, which helps the agent decide whether this tool is appropriate for the user's intent.

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?