Skip to main content
Glama

set_checklist_item

Idempotent

Ticks or unticks a single task checklist item by ID or title, respecting permissions and task state. Signals when all items are done so you can prompt the user to complete the task.

Instructions

Tick or untick one checklist item. item = the item id from get_task, or its exact/unique title.

Same rules as the web app: no changes on a done or deleted task; an item someone else ticked can be unticked only by a project admin. When the last item gets ticked the result says all_items_done: the web app then asks whether to mark the task done, so ask the user and call complete_task (this tool never completes the task itself).

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>",
      "item": "<item>"
    },
    "name": "set_checklist_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemYes
checkedNo
task_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only say this is a non-destructive, idempotent, open-world mutation; the description adds the substantive rules the annotations cannot express — no changes on done or deleted tasks, admin-only unticking of another user's item, and the guarantee that this tool never completes the task. It also names a result field (all_items_done) that drives a follow-up workflow.

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?

Content is front-loaded with the core action first, then identifier semantics, then constraints and the follow-up flow. Every sentence carries information, but a mid-sentence line break ('from\nget_task') and the slightly sprawling final clause cost it a perfect score.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, the description need not enumerate return values, yet it still flags the one result field that matters for agent decision-making (all_items_done). Combined with the mutation rules and identifier guidance, nothing needed to invoke this correctly is missing.

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 description coverage is 0%, so the description must carry the load. It fully explains `item` (id from get_task or exact/unique title), and the tick/untick framing implies the boolean `checked` semantics, though it never states that checked=false is the untick path. `task_id` is left self-evident.

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?

The first sentence gives a specific verb pair and resource: 'Tick or untick one checklist item.' It also pre-empts confusion with the closest sibling by stating 'this tool never completes the task itself', so an agent can distinguish it from complete_task without inspecting 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?

The description covers when the tool applies (ticking/unticking an item), the accepted item identifier ('the item id from get_task, or its exact/unique title'), and the exclusion conditions (done or deleted task, items ticked by someone else requiring project admin). It also routes the agent explicitly: when all_items_done appears, ask the user and then call complete_task.

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