Skip to main content
Glama
cjo4m06

Shrimp Task Manager

split_tasks

Split complex tasks into independent, trackable subtasks with dependencies and priorities. Supports append, overwrite, selective update, and clear all tasks modes.

Instructions

將複雜任務分解為獨立且可追蹤的子任務,建立明確的依賴關係和優先順序。支援四種任務更新模式:追加(append)、覆蓋(overwrite)、選擇性更新(selective)和清除所有任務(clearAllTasks),其中覆蓋模式只會刪除未完成的任務並保留已完成任務,選擇性更新模式可根據任務名稱智能匹配更新現有任務,同時保留其他任務,如果你需要規劃全新的任務請使用清除所有任務模式會清除所有任務並創建備份。請優先使用清除所有任務模式,只有用戶要求變更或修改計畫內容才使用其他模式。

**請參考之前的分析結果提供 pseudocode

**如果任務太多或內容過長,請分批使用「split_tasks」工具,每次只提交一小部分任務

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tasksYes結構化的任務清單,每個任務應保持原子性且有明確的完成標準
updateModeYes任務更新模式選擇:'append'(保留所有現有任務並添加新任務)、'overwrite'(清除所有未完成任務並完全替換,保留已完成任務)、'selective'(智能更新:根據任務名稱匹配更新現有任務,保留不在列表中的任務,推薦用於任務微調)、'clearAllTasks'(清除所有任務並創建備份)。 預設為'clearAllTasks'模式,只有用戶要求變更或修改計劃內容才使用其他模式
globalAnalysisResultNo全局分析結果:來自 reflect_task 的完整分析結果,適用於所有任務的通用部分
Behavior4/5

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

With no annotations, the description explains each update mode's behavior (e.g., overwrite deletes only unfinished tasks, clearAllTasks creates a backup). This discloses key behavioral traits, though it could mention error handling or idempotency.

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 front-loaded with purpose, followed by mode details and usage priority. Some redundancy exists (e.g., repeated mode explanations), but overall it is well-structured and informative.

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 3 parameters, no output schema, and moderate complexity, the description covers all necessary aspects: mode behaviors, usage priority, and batch splitting instructions. It is sufficient for an agent to use the tool correctly.

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 coverage is 100%, so baseline is 3. The description adds value by explaining the updateMode parameter's usage context (when each mode is appropriate) and the tasks' atomicity requirement, enhancing meaning beyond schema.

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?

Clearly states the verb 'split' (分解) and resource 'tasks', and specifies the outcome: creating independent sub-tasks with dependencies and priorities. This distinguishes it from sibling tools like update_task or execute_task.

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 recommends prioritizing the 'clearAllTasks' mode and only using other modes when user requests changes. Also provides guidelines on batching and referencing previous analysis, giving clear when-to-use instructions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/cjo4m06/mcp-shrimp-task-manager'

If you have feedback or need assistance with the MCP directory API, please join our Discord server