Skip to main content
Glama

Get Kanban Board

get_kanban_board
Read-onlyIdempotent

View a GitHub Project v2 as a Kanban board grouped by Status, returning all columns with their items to track work by project status.

Instructions

View a GitHub Project v2 as a Kanban board with items grouped by Status column. Returns all columns with their items.

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": "get_kanban_board"
  }
}

Input Schema

NameRequiredDescriptionDefault
repoNoRepository name - LEAVE EMPTY to auto-detect
ownerNoProject owner - LEAVE EMPTY to auto-detect
item_limitNoMaximum items per column (default 25, max 100). Set to 0 for summary_only behavior.
use_test_dbNo
summary_onlyNoReturn column summaries only (name + itemCount), omitting individual items. Saves ~80% tokens.
project_numberNoGitHub Project number (optional if repo is registered)

Output Schema

NameRequiredDescriptionDefault
codeNoError code (e.g. VALIDATION_ERROR, INTERNAL_ERROR)
hintNo
errorNoHuman-readable error message
ownerNo
columnsNo
detailsNoAdditional error context
categoryNoError category (validation, query, connection, internal)
projectIdNo
suggestionNoSuggested fix for the error
totalItemsNo
instructionNo
recoverableNoWhether the error is recoverable
summaryOnlyNo
detectedRepoNo
projectTitleNo
detectedOwnerNo
itemDirectoryNo
projectNumberNo
statusFieldIdNo
statusOptionsNo
aggregated_errorsNoDetails of individual errors in a multi-step operation
requiresUserInputNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv9.1.0
    • changedInput schema / properties / project_number / type
      Previous value: -"number"New value: +[
      +  "number",
      +  "string"
      +]
  2. First observedv9.0.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so safety is covered. The description adds the useful behavior that items are grouped by the Status column and that all columns are returned, but stays silent on token cost, large-board behavior, and what happens when the project isn't registered — all relevant for an openWorld read.

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, front-loaded with the core purpose and zero filler. The second sentence partly restates the first ('grouped by Status column' vs 'returns all columns with their items'), a minor redundancy that keeps it from a 5.

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?

An output schema exists and the schema documents the parameters well, so the description needn't explain return values or argument formats. What remains missing — guidance versus get_project and large-board/pagination expectations — is minor for a six-parameter, all-optional read tool.

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 83%, so parameters are already well documented in the schema, including auto-detect behavior for repo/owner and the item_limit/summary_only trade-off. The description adds no parameter meaning beyond that, which makes the baseline 3 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 names a specific verb and resource ('View a GitHub Project v2 as a Kanban board') and specifies the grouping rule (items grouped by Status column). That distinguishes it from the raw 'get_project' and 'list_projects' siblings without naming them explicitly.

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?

When-to-use is only implied by the word 'Kanban board' — an agent can infer this is the visual/board-shaped view versus get_project's raw project data. There is no explicit alternative named and no when-not guidance (e.g., 'use summary_only for large boards' is only in the schema).

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