Skip to main content
Glama

KanbanMCP

Delete a column

delete_column
DestructiveIdempotent

Remove a column. If it holds cards, name another column to receive them.

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": {
      "columnId": "<columnId>"
    },
    "name": "delete_column"
  }
}

Input Schema

NameRequiredDescriptionDefault
intoNoThe column that receives its cards. Needed when it holds any.
boardIdNoBoard id or slug.
personaNoThe persona to act as.
columnIdYesA column, by id or label.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered. The description adds non-obvious behavioral context beyond that: the column may hold cards and those cards must be reassigned, which is the key data-loss consideration when invoking this tool.

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?

Two short sentences with the destructive action front-loaded and the conditional card-handling rule immediately after. No filler or redundancy.

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?

For a simple destructive mutation with no output schema, the description covers the primary risk (existing cards) and the required mitigation. It omits permission/auth requirements and whether the operation is recoverable, but these are minor for a tool whose annotations already flag destructiveness.

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 every parameter is already documented in the schema, including `into` as "the column that receives its cards." The description reinforces the conditional nature of `into` but adds no format, syntax, or id/label detail beyond the schema. Baseline 3 applies.

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?

"Remove a column" gives a specific verb (remove) and resource (column), which is clearly distinct from the sibling edit_column. It stops short of naming edit_column as the non-destructive alternative, so an agent must infer that distinction itself.

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

Usage Guidelines3/5

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

The description gives one actionable usage condition — supply another column when the target holds cards — which is genuinely helpful routing for the `into` argument. It offers no guidance on when to prefer this over edit_column or on prerequisites, leaving usage largely implied.

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