Skip to main content
Glama

Set To Do Task State

set_todo_task_state
DestructiveIdempotent

Sets a To Do task's status, importance and extension fields for unattended updates. Use it to change task state safely and idempotently without altering titles, notes, dates or repeat patterns.

Instructions

Set only a To Do task's status, importance and your own extension fields, for unattended use. It can't change the title, notes, dates or repeat pattern, or delete. The same call twice changes nothing more, so a failed call is safe to repeat. Completing a repeating task is refused; use update_todo_task. Complete only tasks you created, and change importance only on tasks carrying your extension, so the person's own choices are never overwritten

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

Input Schema

NameRequiredDescriptionDefault
statusNoNew status
list_idYesTo Do list ID
task_idYesTask ID
extensionNoFields to set in your extension. Fields you leave out keep their values; a missing extension is created
importanceNoNew importance

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Goes well beyond the annotations by explaining its idempotency in operational terms ('the same call twice changes nothing more, so a failed call is safe to repeat'), disclosing the refusal behavior for repeating tasks, and describing partial-extension merge semantics. It also warns against overwriting the person's own choices, which contextualizes the destructiveHint. It stops short of saying whether status/importance changes are reversible or how to undo one.

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?

Three dense but purposeful sentences, front-loaded with the capability and its limits before the safety and ownership caveats. No filler, though the final clause run-on slightly reduces readability.

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 nested, five-parameter mutation tool with no output schema, the description covers what mutates, what is refused, idempotency, and ownership constraints. The main remaining gap is the absence of return-value or partial-failure information, which matters somewhat since no output schema exists.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning: which fields are touched versus preserved, that a missing extension is created and omitted fields keep their values, and that importance writes are restricted to tasks carrying the caller's extension. Enum values themselves are left to the schema.

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 plus an explicit scope limit: it sets only status, importance and the caller's own extension fields. It names the sibling update_todo_task for everything it cannot do (title, notes, dates, repeat pattern, delete), so an agent can route correctly without opening either schema.

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 explicit when-to-use ('unattended use'), when-not (completing a repeating task is refused — use update_todo_task), and additional eligibility rules: complete only tasks you created, change importance only on tasks carrying your extension. Alternatives and exclusions are stated rather than inferred.

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

Deploy Server

Other Tools