Skip to main content
Glama

list_columns

Read-onlyIdempotent

Fetch columns from a Kaiten board by board ID to view titles, types, and order for workflow configuration.

Instructions

List columns on a board (id, title, type, 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": {
      "board_id": "<board_id>"
    },
    "name": "list_columns"
  }
}

Input Schema

NameRequiredDescriptionDefault
board_idYes

Output Schema

NameRequiredDescriptionDefault
countYes
itemsYes
card_idNo
_metricsNo
board_idNo
space_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/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 the safety profile is fully covered elsewhere. The description adds nothing behavioral beyond that, and its parenthetical listing of fields (id, title, type, order) merely restates what the output schema already provides.

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?

One short, front-loaded sentence with no filler. The parenthetical field list is somewhat redundant given the output schema, which keeps it from being optimal.

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 simple read-only list tool with both annotations and an output schema, the description is nearly sufficient. The remaining gap is that it never confirms the required board_id scope or that columns are board-scoped children of list_boards.

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?

There is a single required parameter, board_id, with 0% schema description coverage, so the schema contributes no meaning. The phrase "on a board" loosely ties the call to a board identifier, but the description never names board_id or states that it is required.

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?

"List columns on a board" states a specific verb and resource, and 'columns' is clearly distinguishable from siblings like list_boards, list_tasks, and list_lanes. It does not explicitly name an alternative, but the resource noun alone differentiates it adequately.

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 gives no when-to-use guidance, no prerequisites, and no alternatives. An agent can infer it is needed to discover column ids before acting on tasks, but that inference comes from the sibling names, not from the definition itself.

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