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

workspace-board-mcp

by FURYER
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

Update board card

board_update_card

Update title and body of a board card by specifying the card ID and workspace path.

Instructions

Update title and/or body of a card (T-N / #T-N).

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

Input Schema

NameRequiredDescriptionDefault
bodyNo
titleNo
card_idYesCard id like T-12
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.7/5.0
Behavior3/5

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

No annotations provided, so description carries the full burden. It states the tool is an update operation (mutation) and provides the card ID format, but does not disclose potential side effects, permission requirements, or whether fields are overwritten or merged.

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 with no wasted words. Includes the card ID format hint in parentheses. Every element earns its place.

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?

Tool is simple (update card fields) and sibling tools provide context. However, no output schema means the return value is undocumented; description does not mention what is returned on success, which is a minor gap for a mutation tool.

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 50% with descriptions for card_id and workspace. The description adds that title and body are updatable, partly compensating for the missing schema descriptions. However, it does not specify allowed formats or constraints for these fields.

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?

Description clearly states the verb 'update' and the resource 'card', specifies updatable fields 'title and/or body', and includes the card ID format hint '(T-N / #T-N)'. It effectively distinguishes from sibling tools like board_add_card and board_delete_card.

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?

Implied usage context: when needing to modify a card's title or body. No explicit when-not or alternatives are provided, which is acceptable given the distinct purpose among siblings, but lacks guidance on prerequisites or when to use other tools.

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