Skip to main content
Glama

restore_task

Restore a previously deleted task using its task ID, undoing the deletion so the task can be accessed and managed again.

Instructions

Undo delete_task for a task id deleted earlier.

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": "restore_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
task_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=true, so the safety profile is covered without description help. The description adds the precondition that the task must have been deleted earlier, but it does not disclose the meaningful non-idempotent behavior (a second restore presumably fails) or the scope of restoration (comments, subtasks, labels).

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?

One short sentence with the operation front-loaded and no filler. It is slightly elliptical in phrasing ('Undo delete_task for a task id deleted earlier'), but nothing is wasted.

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?

An output schema exists, so return values need no explanation, and the tool is a simple single-parameter mutation. The remaining gap is whether restoration is partial or full and how it relates to reopen_task, which keeps it from a 5.

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?

There is a single parameter with 0% schema description coverage, so the schema supplies no semantics at all. The description partially compensates by indicating task_id refers to a task that was previously deleted, which is real added meaning, but it doesn't state the format, source (e.g., from a prior listing or delete response), or failure mode for invalid ids.

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?

The description states a specific verb+resource ('Undo delete_task') and ties the operation to a prior deletion, which distinguishes it from generic mutation siblings like update_task or edit_task. It falls short of 5 because it doesn't explicitly separate restore_task from reopen_task, which an agent could easily confuse with it.

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 phrase 'for a task id deleted earlier' implies a precondition (the task must already have been deleted), which is useful implied guidance. However, there is no explicit statement of when not to use it, no mention of reopen_task as the alternative for non-deleted tasks, and no note about what happens if the id was never deleted.

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