Skip to main content
Glama
Sign In
workspace-board-mcp

workspace-board-mcp

by FURYER
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

Move board card

board_move_card

Move a card to another column in a workspace kanban board, with optional ordering within the destination column.

Instructions

Move a card to another column (and optional 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": {
      "workspace": "<workspace>",
      "card_id": "<card_id>",
      "column_id": "<column_id>"
    },
    "name": "board_move_card"
  }
}

Input Schema

NameRequiredDescriptionDefault
orderNoOrder within the column
card_idYesCard id like T-12
column_idYesDestination column id
workspaceYesAbsolute path to the project workspace root (contains .webcli/board.json)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations exist, so the description bears full burden. It implies a mutation but does not disclose side effects, reversibility, or response. More transparency is needed for a move operation.

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?

The single-sentence description is concise and front-loaded with the core action. However, it is slightly too minimal and could benefit from a bit more context without losing conciseness.

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?

The tool has moderate complexity with 4 parameters. The description covers the primary function but lacks usage context, behavioral details, and any reference to output. It is adequate but not fully complete.

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%, so the baseline is 3. The description does not add meaning beyond the schema; it merely restates the optional order. No extra context is provided.

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 clearly states the verb 'move', resource 'card', and specifies destination 'another column' with optional order. This distinguishes it from siblings like add, delete, or update.

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?

No guidance is provided on when to use this tool vs alternatives like board_add_card or board_update_card. No prerequisites, error conditions, or exclusions are mentioned.

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