Skip to main content
Glama

Check off a shared list item

zarok_set_shared_list_item_done

Marks one shared list item done, or not done again with done=false. Other members see who checked it off. Not covered by the 24-hour plan undo: a call with the opposite value reverses it. Requires an editor or owner role.

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>",
      "item_id": "<item_id>",
      "done": "<done>"
    },
    "name": "zarok_set_shared_list_item_done"
  }
}

Input Schema

NameRequiredDescriptionDefault
doneYestrue to check the item off, false to uncheck it
item_idYesThe item id from zarok_get_shared_lists with list_id
list_idYesA shared list id from zarok_get_shared_lists

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / done / description
      Added value: +"true to check the item off, false to uncheck it"
    • addedInput schema / properties / item_id / description
      Added value: +"The item id from zarok_get_shared_lists with list_id"
    • addedInput schema / properties / list_id / description
      Added value: +"A shared list id from zarok_get_shared_lists"
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Adds substantial behavior beyond the annotations: attribution ('Other members see who checked it off'), an explicit undo caveat ('Not covered by the 24-hour plan undo'), and the reversal mechanism. These are exactly the facts an agent needs before mutating shared state.

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?

Four short sentences, each carrying a distinct fact, with the primary action front-loaded. Nothing is redundant with the title or schema.

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?

For a three-parameter mutation with no output schema, the description covers purpose, auth requirement, undo behavior, and social side effects. An agent has everything needed to invoke it correctly.

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 coverage is 100%, so all three parameters are already fully documented, which sets the baseline at 3. The description only reinforces the meaning of done=false; it adds no new syntax or format detail.

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 ('Marks one shared list item done, or not done again with done=false') and covers both directions of the toggle in one clause. An agent can distinguish this from zarok_add_shared_list_item 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 Guidelines4/5

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

Gives clear prerequisites ('Requires an editor or owner role') and an explicit reversal path ('a call with the opposite value reverses it'). It does not name a sibling alternative, which keeps it just short of a 5.

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