Skip to main content
Glama

get_board

Read-only

Displays a Kanboard project's board with each column and its open tasks in order, so you can review workflow status at a glance.

Instructions

Show a project's board: each column with its open tasks, in order.

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": {
      "project_id": "<project_id>"
    },
    "name": "get_board"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idYesKanboard project ID

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds genuine behavioral context by stating the result is organized into columns and limited to open tasks in order, but it says nothing about ordering rules, pagination, or limits on task counts per column.

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?

One sentence, front-loaded with the action and resource, with the structural detail appended. Nothing is wasted and nothing important is buried.

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?

The tool is simple and read-only with an output schema, so return values need not be explained; the description still sketches the response shape. The only shortfall is the absence of any routing guidance against the many sibling task-listing tools, which matters given how similar they sound.

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 coverage is 100% with a single documented project_id (positive integer), so the schema carries the parameter burden. The description only implies that the board belongs to a project, adding no format or constraint detail beyond the schema — the baseline 3 for full coverage 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 gives a specific verb and resource ('Show a project's board') and adds scope detail ('each column with its open tasks, in order'), so the agent knows this is a board/column view rather than a flat task list. It does not name or contrast with siblings such as list_tasks or get_task, so differentiation is left to inference.

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?

Usage is only implied: the word 'board' and the 'open tasks' scoping suggest this is the Kanban-view alternative to a flat list, but there is no explicit when-to-use, when-not-to-use, or named alternative. An agent must infer that this is not the tool for filtering or for closed tasks.

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