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

workspace-board-mcp

by FURYER
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

Add board card

board_add_card

Create a new card in a workspace kanban board. Provide workspace path and card title; optionally add notes and select a column.

Instructions

Create a card (id T-N). Defaults to first column (Inbox) if column_id omitted.

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>",
      "title": "<title>"
    },
    "name": "board_add_card"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyNoOptional notes/body
titleYesCard title
column_idNoTarget column id (e.g. col_inbox)
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

A3.9/5.0
Behavior3/5

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

With no annotations provided, the description carries full burden. It discloses the default column behavior (important side effect), but does not mention response format, idempotency, error conditions, or permission requirements. Adequate but not thorough.

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?

Single sentence that conveys the core action and a key behavioral nuance. No extraneous information. Front-loaded with verb and resource.

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?

Simple tool with 4 parameters, no output schema. Description covers creation and default column behavior. However, it misses details like expected return value, error scenarios (e.g., duplicate title), and potential side effects beyond the default. Adequate for basic use but could be more complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, giving a baseline of 3. The description adds value by specifying that column_id defaults to the first column (Inbox) if omitted, which is meaningful behavioral context not captured in the schema.

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 'Create a card (id T-N)' with a specific verb and resource. It distinguishes from sibling tools like board_update_card or board_delete_card by focusing on creation. The default column behavior adds clarity.

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?

The description provides guidance on omitting column_id to use the default first column, but does not explicitly state when to use this tool vs alternatives like board_update_card or board_add_column. Some implied usage context, but lacks exclusions or comparative guidance.

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