Skip to main content
Glama
Sign In
kanbn-mcp

kanbn-mcp

by kjduling
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

kanbn_ensure_board

Ensure a Kanbn board exists at the given project path, creating it with the specified columns when not already initialized.

Instructions

Ensure a Kanbn board exists, initializing one if absent (board detection checks the methods: initialised, initialized, isInitialized, isInitialised).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "kanbn_ensure_board"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoName of the board
pathNoPath to the project root directory
columnsNoInitial board columns

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv1.1.0
    • addedInput schema / properties / columns
      Added value: +{
+  "description": "Initial board columns",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
    • removedInput schema / properties / dates
      Removed value: -{
-  "description": "Filter stats by a date range: a single ISO date or an array of two ISO dates",
-  "oneOf": [
-    {
-      "type": "string"
-    },
-    {
-      "items": {
-        "type": "string"
-      },
-      "type": "array"
-    }
-  ]
-}
    • removedInput schema / properties / due
      Removed value: -{
-  "description": "Show overdue tasks and time remaining",
-  "type": "boolean"
-}
    • addedInput schema / properties / name
      Added value: +{
+  "description": "Name of the board",
+  "type": "string"
+}
    • removedInput schema / properties / quiet
      Removed value: -{
-  "description": "Return partial status (task counts only)",
-  "type": "boolean"
-}
    • removedInput schema / properties / sprint
      Removed value: -{
-  "description": "Show sprint stats for a named or numbered (1-based) sprint; defaults to the current sprint when omitted",
-  "oneOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "number"
-    }
-  ]
-}
    • removedInput schema / properties / untracked
      Removed value: -{
-  "description": "Include a list of untracked task files (with quiet, returns just that list)",
-  "type": "boolean"
-}
  2. First observedv1.0.2

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the behavioral disclosure burden. It adds a useful implementation detail about board detection methods (initialised, initialized, isInitialized, isInitialised) and implies idempotency ('if absent'). However, it does not state what happens if the board already exists (no-op vs error), whether it modifies existing boards, or what the return value is. These gaps are notable for a tool without annotations.

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 sentence with no filler. The main action is front-loaded, and the parenthetical detail about detection methods is relevant and compact. Every part contributes to understanding the tool.

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?

Given no output schema and no annotations, the description should clarify what the tool returns or how it behaves on an existing board. It gives enough to invoke it, but the lack of a specified return value and explicit 'already exists' behavior leaves an agent guessing about the outcome. For a setup-style tool, this is a moderate gap.

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 the three parameters (name, path, columns) are already documented. The description adds no additional meaning about parameters—it focuses on the tool's behavior rather than clarifying how name, path, or columns affect initialization. Baseline 3 is appropriate.

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 clearly states a specific verb and resource: 'Ensure a Kanbn board exists, initializing one if absent.' It conveys the idempotent ensure behavior, distinguishing it from plain creation or existence checks, though it does not explicitly name any sibling tool.

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 clear context: use this when you need a board to exist, with initialization if missing. This implies a setup/ensure workflow, but it does not explicitly contrast with alternatives like kanbn_create_board, kanbn_init_board, or kanbn_board_exists, nor does it mention any exclusions or prerequisites.

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