Skip to main content
Glama
Sign In
kanbn-mcp

kanbn-mcp

by kjduling
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

kanbn_search

Find tasks on a Kanban board by applying filters for status, assignee, tags, dates, custom fields, and more across all columns.

Instructions

Search tasks on the board with filters (works across all columns).

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_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNoPath to the project root directory
quietNoIf true, return only matching task IDs (default: false)
filtersNoTask filters: id, name, description, column, assigned, sub-task, tag, relation, comment (regex strings), created, updated, started, completed, due, plannedStart, plannedFinish (dates or ranges), workload, progress, count-sub-tasks, count-tags, count-relations, count-comments (numbers or ranges), overdue, is-started, is-completed, in-started-column, in-completed-column (booleans), plus any configured custom fields

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does not explicitly state that the tool is read-only, what kind of results it returns (full tasks vs. IDs), how the 'quiet' flag alters output, or any side effects. The verb 'Search' hints at a read operation, but this is not stated, leaving the agent to guess at critical behavioral details.

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?

A single sentence with no wasted words: it states the action, resource, mechanism, and a key scope qualifier. The parenthetical adds valuable differentiation without bloating the description. Every word earns its place, and the most important information is front-loaded.

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?

The tool is complex: it has a nested filters object, an optional quiet flag, and no output schema. The description does not explain what the output looks like, how filters are combined, whether results are sorted, or how the quiet flag changes the response. For a search tool of this complexity, the description leaves too much to be inferred and is therefore incomplete.

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 parameters are already fully documented in the schema, including the complex 'filters' object with its many keys. The description adds no extra meaning beyond the generic term 'filters', which matches the baseline for high schema coverage. It neither compensates nor harms parameter understanding.

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 action ('Search tasks on the board') and resource ('tasks'), and the parenthetical 'works across all columns' provides a meaningful scope qualifier that distinguishes it from column- or board-specific tools. However, it does not explicitly name or contrast with sibling lookup tools like kanbn_find_simple_tasks or kanbn_get_task, so it falls just short of full sibling differentiation.

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 phrase 'works across all columns' gives implicit context that this tool is appropriate when the search must span the entire board rather than a single column or status, but the description provides no explicit when-to-use or when-not-to-use guidance and names no alternatives. It is adequate as an implied usage hint, not a clear routing instruction.

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