Skip to main content
Glama
Sign In

Milanote MCP Server and API by Cotlet

by dev.cotlet
OverviewDiscussionsAdmin

Set task done

set_task_done
Destructive

Tick or untick one task in a to-do list. Finds the task by task_id or by its exact text and sets it done or not done, as clicking its checkbox does; the rest of the list stays as it was. Returns the whole list after the change. When two tasks share the text, pass the task_id instead.

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": {
      "board_id": "<board_id>",
      "card_id": "<card_id>",
      "task": "<task>"
    },
    "name": "set_task_done"
  }
}

Input Schema

NameRequiredDescriptionDefault
doneNotrue ticks it, false unticks it. Default true.
taskYesThe task's task_id from get_board, or its exact text.
card_idYesTo-do list ID from get_board.
board_idYesBoard ID from list_boards, or the board URL.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

With annotations present, the description still adds real value: it says the rest of the list is untouched, that the change mirrors clicking a checkbox, and that the full list is returned. It does not address the destructiveHint=true / openWorldHint=true profile or any auth concerns, leaving a small gap.

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?

Three tight sentences: core action first, then side-effect scope and return value, then the ambiguity edge case. Every sentence earns its place with no repetition of the title.

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?

There is no output schema, and the description compensates by stating the whole list is returned. Combined with the ambiguity guidance and the untouched-rest-of-list guarantee, an agent could call this correctly; only the destructive/open-world annotation implications are left unexplained.

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; the description goes beyond it by explaining the task/task_id trade-off under ambiguity, which the schema does not. The done and board_id parameters still rely entirely on schema text.

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 description states a concrete verb and resource: tick/untick a single task in a to-do list, found by task_id or exact text. This is clearly distinguishable from siblings such as add_todo_list, move_card, or get_board, and the checkbox analogy pins down the exact semantics.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives a clear disambiguation rule: use task_id when two tasks share the same text. It does not enumerate alternatives or prerequisites beyond pointing at get_board/board ids via the schema, so it stops short of full when/when-not coverage.

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

All Milanote MCP Server and API by Cotlet toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources