Skip to main content
Glama

set_checkitem_state

Mark a Trello checklist item complete or incomplete by specifying the card, checklist item, and target state.

Instructions

Mark a checklist item complete or incomplete.

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": {
      "cardId": "<cardId>",
      "checkItemId": "<checkItemId>",
      "state": "<state>"
    },
    "name": "set_checkitem_state"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoISO 639-1 code of the language the user is writing in (e.g. en, ru, uk). Always pass it: server messages are returned in this language.
stateYes
cardIdYes
checkItemIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, so the mutation/safety profile is covered by structured data. The description adds nothing beyond that — it does not say whether re-setting the same state is harmless, whether the card is modified in other ways, or what a failure looks like. Setting a target state rather than toggling is mildly informative but largely restates the enum.

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?

A single front-loaded sentence with zero filler and no repetition. It is efficient, though its brevity contributes to the gaps in guidance rather than compensating for them.

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

Completeness2/5

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

This is a mutation tool with no output schema, 4 parameters at 25% description coverage, and no annotations explaining side effects or return behavior. The description does not fill any of that space, so an agent knows the intent but not the contract.

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

Parameters2/5

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

Schema description coverage is only 25%: only lang is documented, while cardId, checkItemId and state carry no schema text. The description names the two states, which duplicates the enum, but says nothing about cardId or checkItemId, leaving half the required surface to inference from parameter names.

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 (mark) and resource (checklist item) plus the two target states, so an agent can tell this sets an item's state rather than creating or deleting one. It does not distinguish itself from adjacent siblings such as add_checklist_item or delete_checklist beyond the implicit difference in operation.

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

Usage Guidelines2/5

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

There is no guidance on when to call this versus alternatives, no mention of prerequisites such as needing a valid cardId/checkItemId pair, and no note on whether the call is idempotent. The agent must infer everything from the name and schema.

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