Skip to main content
Glama
Sign In

TaskLite

by net.tasklite
OverviewDiscussionsAdmin

reorder_columns

Idempotent

Set the display order of a board's columns. Pass every column id in the wanted order (get_board_schema lists them).

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": {
      "projectId": "<projectId>",
      "boardId": "<boardId>",
      "columnIds": "<columnIds>"
    },
    "name": "reorder_columns"
  }
}

Input Schema

NameRequiredDescriptionDefault
boardIdYesBoard id (from list_boards / create_board)
columnIdsYesColumn ids in the new order (every column of the board)
projectIdYesProject id (from list_projects / create_project)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / boardId / description
      Added value: +"Board id (from list_boards / create_board)"
    • addedInput schema / properties / columnIds / description
      Added value: +"Column ids in the new order (every column of the board)"
    • addedInput schema / properties / projectId / description
      Added value: +"Project id (from list_projects / create_project)"
  2. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already establish mutating, idempotent, non-destructive behavior. The description adds that the order is set as a complete list rather than a partial patch, which is useful, but it does not disclose response behavior or failure modes. This is adequate but not rich.

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?

Two tight sentences with no filler. The core action comes first, and the critical full-list requirement is stated in the second sentence.

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?

For a three-parameter reorder tool with a fully documented schema and safe/idempotent annotations, the description is nearly complete. It covers the full-set requirement and points to get_board_schema; it only omits explicit output/failure details, which are less critical here.

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% and the columnIds schema already states 'new order' and 'every column of the board.' The description's main added value is pointing to get_board_schema as the source for valid column ids, which is helpful but not a substantial semantic addition.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb ('Set') and a precise resource ('display order of a board's columns'), which distinguishes it from siblings like create_column, update_column, and delete_column. The action is immediately clear and not a tautology.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives clear operational context: pass every column id in the wanted order and use get_board_schema to obtain those ids. It does not explicitly name alternatives or exclusion conditions, but for a simple reorder operation the context is sufficient.

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

All TaskLite toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources