Skip to main content
Glama

Coline

Restore a task

restore_task
Idempotent

Puts a deleted task back with its id, number where free, assignees, fields, relations and sub-tasks.

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": {
      "workspace": "<workspace>",
      "taskboardId": "<taskboardId>",
      "taskId": "<taskId>"
    },
    "name": "restore_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskIdYesTask id from list_tasks, find_task or get_task.
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".
taskboardIdYesBoard id from list_boards.

Output Schema

NameRequiredDescriptionDefault
taskYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare non-read-only, idempotent, non-destructive, so safety is covered; the description adds genuine context beyond that by disclosing exactly which attributes are reinstated and the notable caveat 'number where free', implying the task number may not come back if it has been reused. It omits permission requirements and failure behavior when restoration conflicts.

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?

A single front-loaded sentence carrying only operative information — what the tool does and what state comes back — with no filler, preamble, or redundancy.

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?

Given an output schema exists (so return structure needn't be described), three fully documented required parameters, and annotations covering the mutation profile, the description supplies what an agent still lacks: the restoration scope and the partial-restore caveat. Only permission/error conditions remain unstated, which is a minor gap for a restore operation.

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 description coverage is 100% and all three required parameters are documented in the schema with explicit source references (list_tasks, workspaces.list, list_boards), so the description adds nothing further about parameters. Baseline 3 applies since the schema does the work.

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 gives a specific verb ('Puts a deleted task back') plus the resource ('task') and enumerates what comes back with it (id, number, assignees, fields, relations, sub-tasks), which is far more informative than the title alone. It does not explicitly contrast with siblings like undo_task_change or create_task, but the 'deleted task' scope keeps it distinguishable.

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?

Usage is only implied: the phrase 'deleted task' signals the precondition that the task must be in a deleted state, but there is no explicit when-to-use, when-not, or named alternative (e.g. undo_task_change vs restore for a soft-deleted task). An agent can infer the context but must guess at the boundaries.

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