Skip to main content
Glama

KanbanMCP

Toggle a checklist item

toggle_task

Flips a checklist item on a card between done and not done, or sets it to a given state. Pick the item by position or by text.

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

Input Schema

NameRequiredDescriptionDefault
doneNoSet it to this instead of flipping it.
textNoThe item's text, instead of a position.
indexNoThe item's position, from 1.
cardIdYesCard id, number (12) or key (WEB-12).
boardIdNoBoard id or slug.
personaNoThe persona to act as.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly=false, destructive=false, and idempotent=false, and the 'flips' wording is consistent with the non-idempotent hint. The description adds the selection mechanism (position or text) but says nothing about auth needs, ambiguity when text matches multiple items, or error behavior, so it adds only modest context.

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?

Two short sentences, with the core action front-loaded and the selection modes compactly appended. Both sentences carry information, though the second is largely a restatement of schema content rather than new guidance.

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

Completeness3/5

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

For a six-parameter mutation tool with no output schema, the safety profile is covered by annotations and parameters are fully documented in the schema, so the definition is minimally sufficient. It falls short on interaction rules an agent would want, such as precedence when both index and text are supplied or what happens on an ambiguous text match, and it never mentions the boardId/persona scoping.

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 description coverage is 100%, so all six parameters are already documented, giving a baseline of 3. The description restates the done-vs-flip distinction already present in the schema and adds no syntax or precedence rules beyond it.

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?

States a specific verb and resource ('flips a checklist item on a card between done and not done') plus the alternate set-to-state behavior. It's clear what the tool does, but it never distinguishes itself from plausible siblings like 'complete' or 'update_card', so an agent must infer the boundary.

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 explicit when-to-use or when-not-to-use guidance. The phrase 'or sets it to a given state' implies the done parameter is the non-flipping path, but the description never says when to prefer toggling over a sibling such as 'complete'.

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