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

workspace-board-mcp

by FURYER
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

Get task board

board_get

Load the workspace kanban board from board.json. Optionally get a single card by providing its card ID.

Instructions

Load the workspace kanban board from .webcli/board.json. Optional card_id (e.g. T-12 or #T-12) returns one card.

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

Input Schema

NameRequiredDescriptionDefault
card_idNoOptional card id like T-12 or #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

A4/5.0
Behavior4/5

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

No annotations provided, so description carries full burden. It clearly indicates a read-only load operation with optional filtering. Does not mention side effects, which are presumably absent. Lacks explicit read-only declaration, but verb and context suffice.

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 sentences, no waste. First sentence states main action and source, second adds optional behavior. Every sentence adds value.

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 simple read tool without output schema, description covers the main behavior and optional parameter. Could clarify error cases (e.g., missing file) but not essential. Complete enough given tool simplicity.

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 description coverage is 100% (both parameters have descriptions). Description restates the schema info but does not add new semantic details beyond format examples for card_id. Baseline 3 appropriate.

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 verb 'Load', resource 'workspace kanban board', and source '.webcli/board.json'. It also specifies optional card_id behavior. Distinguishes from sibling mutation tools (e.g., board_add_card, 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?

No explicit guidance on when to use or not use this tool versus alternatives. Usage is implied by the read nature, but lacks direct comparison or exclusion statements.

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