独行录 / 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.

Changed1 schema field changedSep 30, 2026

addedInput schema / properties / plan / properties / derivedFromId

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

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.7/5.0

Behavior4/5

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

Adds substantial context beyond the annotations: default PRIVATE+DRAFT, the rule that only GENERAL with explicit consent may be PUBLIC, the PRIVATE+PUBLISHED targeted-send semantics, and the completeness checklist required before publishing. It does not cover concurrency (expectedUpdatedAt) or permission prerequisites for saving, which is why it falls short of 5.

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?

Front-loads the core action and the save-authorization rule before drilling into field semantics. It is dense and long, but nearly every clause carries operative rules rather than filler.

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 write tool with no output schema and a deeply nested 2-parameter object schema, the description supplies the decision rules, defaults, enum semantics, and formatting constraints an agent needs to invoke it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the full burden and does so: it defines purpose enum semantics (GENERAL/TARGETED/targetUserId, LEGACY not newly sendable), visibility rules, status meaning, contentFormat with supported markdown syntax, and sectionTitles constraints.

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?

States a precise verb pair (新增或编辑) plus the resource (本人合作方案), and its scope is immediately separable from siblings like get_cooperation_plan, list_cooperation_plans, delete_cooperation_plan, and edit_cooperation_plan_with_agent.

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?

Explicitly states when to call (仅明确要求保存才调用) and when not (只看或改草稿不授权保存，待确认不等于已保存), and routes the purpose-change / legacy-draft case to the named alternative Agent ADAPT_PURPOSE with a preview-confirm step.

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?