Skip to main content
Glama

complete_task

Mark a TickTick task as completed or finish up to 50 tasks in one project; omit projectId with taskIds to use the inbox.

Instructions

Mark one TickTick task completed, or complete up to 50 tasks in one project by passing taskIds. For taskIds, omit projectId to use the inbox.

Input Schema

NameRequiredDescriptionDefault
taskIdNoTickTick task ID for a single task.
taskIdsNoTask IDs to complete in one project.
projectIdNoProject ID. Required for taskId; optional for taskIds means the inbox.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.1

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare a non-read-only, non-destructive mutation, so the safety profile is covered. The description adds the batch size ceiling and inbox default, but says nothing about partial failures when completing up to 50 IDs, behavior on already-completed tasks, or idempotency — the traits that actually matter for a bulk mutation.

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?

Two short sentences with zero filler, leading with the single-task case before the batch case. Nothing is repeated or wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a bulk mutation with no output schema, an agent still cannot tell what the call returns — per-ID success/failure, error aggregation, or whether any completion occurs on partial validation failure. The description also omits the parameter relationship (projectId required for single taskId, optional for taskIds) that the schema only implies across two branches.

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

Parameters3/5

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

Schema coverage is 100%, so all three parameters are documented in the schema, including the inbox default for omitted projectId. The description restates the same facts without adding format, ordering, or constraint detail beyond the schema, so the baseline of 3 applies.

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 specific verb and resource ('Mark one TickTick task completed') and immediately extends it to a bounded batch mode ('up to 50 tasks in one project'). This makes it distinguishable from mutation siblings like update_task, which change fields but do not complete a task.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear mode-selection guidance: use taskId for a single task, taskIds for a batch, and omit projectId to target the inbox. It does not mention when to prefer update_task or how completion interacts with recurring tasks, but the core either/or is explicit.

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