Skip to main content
Glama

Complete several tasks

complete_tasks
Idempotent

Mark up to 50 tasks as done (or done=false to reopen them) in one call. One undo_last_change reverts the whole call.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "ids": "<ids>"
    },
    "name": "complete_tasks"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYes
doneNotrue = done (default), false = not done.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds genuinely non-obvious behavior: the hard cap of 50 ids per call and the fact that a single undo_last_change reverts the entire batch as one unit, which the agent cannot learn from the schema or annotations. It does not say what happens when some ids are invalid or duplicated, so partial-failure semantics remain undisclosed.

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, no filler, and the most decision-relevant fact (the 50-task batch scope) is front-loaded. The undo note follows as a compact caveat and earns its place.

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?

For a low-complexity batch mutation with annotations covering safety and idempotency and no output schema, the definition covers scope, the reverse operation, and undo atomicity. The only material gap is failure behavior for mixed valid/invalid id lists, which an agent would want before calling with a large batch.

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 50%: ids is documented (source tools, repeat_… ids, length bounds, max 50) and done is documented with its default. The description adds meaning to done=false by framing it as "reopen them" rather than merely "not done," which is a real semantic gain. It adds nothing beyond the schema for ids, so with half the parameters already documented this is a minimum-viable 3.

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?

"Mark up to 50 tasks as done" states a specific verb (mark done), resource (tasks), and a cardinality scope that implicitly distinguishes this batch tool from the singular complete_task sibling. However, it never names complete_task or another alternative explicitly, so the agent must infer the batch-vs-single routing on its own.

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

Usage Guidelines3/5

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

The description implies the batch use case ("up to 50 tasks ... in one call") and mentions done=false for reopening, which gives the agent some usage context. It offers no explicit when-not guidance or named alternative, so choosing between this and complete_task, update_tasks, or delete_tasks is left to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources