Skip to main content
Glama

complete_task

DestructiveIdempotent

Da una tarea por terminada: pasa a completed y le escribe completed_at.

Usar cuando la persona confirma que la hizo, no cuando lo parece. Para
desmarcarla va rollback_task, que además limpia la fecha de cierre — con
update_task la tarea vuelve al radar arrastrando el día en que se cerró.

Fuera de Secondbrain: si la tarea está en ClickUp o Jira, se cierra también allá. Si ya estaba completada, no hace nada.

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": {
      "task_id": "<task_id>"
    },
    "name": "complete_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
task_idYesID numérico de la task
workspace_idNoUUID del workspace, o su nombre tal como lo dice el usuario ('Acme', 'el personal'). Omitir si el token ya tiene workspace fijo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare destructiveHint, idempotentHint and openWorldHint, but the description adds concrete meaning: the external sync to ClickUp/Jira, and the idempotent no-op when the task is already completed. It does not discuss permissions or error cases, but the added context is well beyond the annotations.

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-loaded with the state change, then the trigger condition, then the alternatives, then the out-of-scope behavior. Every sentence carries information; slightly dense but no filler.

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 2-parameter mutation with no output schema, this covers the trigger, the state effect, cross-system behavior and idempotency. Missing only error handling (e.g. task not found) and confirmation of the response, which are minor given the tool's simplicity.

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% — both task_id and workspace_id are documented in the schema, including the fallback of omitting workspace_id when the token is bound. The description adds nothing about parameters, 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?

Opens with a specific verb plus resource plus the exact state transition: 'Da una tarea por terminada: pasa a `completed` y le escribe `completed_at`.' An agent knows precisely what changes, and the following sentences separate it from rollback_task and update_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?

Gives an explicit trigger ('cuando la persona confirma que la hizo, no cuando lo parece') with a negative condition, and names the correct alternative for the reverse operation (rollback_task) while explaining the pitfall of using update_task (it leaves the closing date set). Nothing 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