Skip to main content
Glama
Sign In
kanbn-mcp

kanbn-mcp

by kjduling
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

kanbn_sort_column

Sort a Kanban board column by task fields (name, created, modified, due, assigned, progress) with ascending/descending order and optional filter. Specify the column name and sorter list to reorder tasks in the project.

Instructions

Sort a board column by the given sorters.

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": {
      "columnName": "<columnName>",
      "sorters": "<sorters>"
    },
    "name": "kanbn_sort_column"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNoPath to the project root directory
saveNoPersist the sort order to the index (default false)
sortersYesList of sorter objects with field (name, created, modified, due, assigned, progress), order (ascending, descending) and optional filter
columnNameYesName of the column to sort

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are available, so the description carries the full burden of behavioral transparency. It only states that a sort occurs, without disclosing side effects, persistence consequences, reversibility, or how multiple sorters and filters combine. The schema hints at persistence through the save parameter, but the description itself does not.

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?

The description is a single front-loaded sentence with no wasted words. It clearly conveys the core action and resource without padding.

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 moderately simple operation, the description plus the detailed input schema is minimally adequate for invoking the tool. However, it lacks context about return values, preconditions, and the practical effect of persisting a sort, leaving some gaps for an agent to fill.

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%, with all four parameters documented in the input schema. The description adds no new parameter-level meaning, so it is adequate but does not go beyond the structured schema.

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 names a specific action ('Sort'), a specific resource ('a board column'), and the method ('the given sorters'). It is immediately clear what the tool does and it stands apart from the sibling tools, none of which focus on sorting a column.

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?

The description provides no guidance on when to use this tool versus alternatives, nor any exclusions or prerequisites. It does not mention board initialization, column existence, or how the save flag affects when this tool should be used.

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

Deploy Server

Other Tools