Skip to main content
Glama
evalor
by evalor

Complete Task(s)

complete_task

Mark tasks as completed in your Dida365 project. Supports batch completion to finish multiple tasks at once.

Instructions

Mark one or more tasks (任务) as completed (已完成). Supports batch completion.

WHEN TO USE:

  • User finished a task and wants to mark it done (完成任务)

  • Batch complete multiple related tasks

WHEN NOT TO USE:

  • Delete a task permanently (删除任务) → use 'delete_task'

  • Update other task properties (修改任务) → use 'update_task'

REQUIRED (per task):

  • projectId: Project containing the task (清单ID)

  • taskId: Task to mark complete (任务ID)

INPUT FORMAT: { "tasks": [{ "projectId": "...", "taskId": "..." }, ...] }

⚠️ IDEMPOTENT: Completing an already-completed or non-existent task returns success. Use 'get_task' first to verify if needed.

⚠️ NOTE: Completed tasks (已完成任务) are no longer returned by 'list_tasks' or 'get_project_data'.

BATCH BEHAVIOR: Non-atomic - some may succeed while others fail. Check summary.failed > 0.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tasksYesArray of tasks to complete
Behavior5/5

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

With no annotations, the description fully discloses key behaviors: idempotency (completing already-completed or non-existent returns success), that completed tasks are hidden from list/get tools, and non-atomic batch execution.

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

Conciseness5/5

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

Well-structured with clear sections, emoji highlights, and no redundant information. Every sentence adds value despite being longer than minimal.

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?

Covers purpose, usage, parameters, and behavioral notes. However, it lacks a description of the return output structure (beyond mentioning 'summary.failed'), which would be helpful for full completeness.

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% with clear descriptions for projectId and taskId. The description adds the required input format, clarifies Chinese terms, and provides context on usage, going 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?

The description clearly states the tool marks one or more tasks as completed, supports batch completion, and distinguishes from siblings like delete_task and update_task in the WHEN NOT TO USE section.

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?

Explicit WHEN TO USE (user finished a task, batch complete) and WHEN NOT TO USE sections, naming specific alternatives (delete_task, update_task) and noting idempotent behavior.

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/evalor/Dida365MCP'

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