Skip to main content
Glama
Sign In
Boarderless MCP Server

Boarderless MCP Server

by CrackenReleased
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Set Board Workspace

set_board_workspace
Destructive

Set the absolute path to your project directory to enable Boarderless to find and manage board files. Use this when the MCP process starts outside the intended workspace.

Instructions

Set the absolute local workspace directory used for automatic and explicit .bdrl.json board files. Call this once at the beginning of work when the MCP process was not launched from the intended project directory.

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": {
      "directory": "<directory>"
    },
    "name": "set_board_workspace"
  }
}

Input Schema

NameRequiredDescriptionDefault
directoryYesAbsolute path to the agent's current project/workspace directory.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.28

TDQS

A4.3/5.0
Behavior4/5

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

Annotations indicate destructiveHint=true; description reinforces it's a setter that changes state. Adds timing advice but doesn't elaborate on what is destroyed. Adequate given annotations.

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, front-loaded purpose, no extraneous words. Efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool is simple with one parameter and no output schema. Covers purpose, parameter, and usage timing. No gaps.

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 already provides a good description for the single parameter. Description does not add new semantics beyond reinforcing 'absolute local workspace directory'. Baseline 3 for 100% coverage.

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?

Clearly states verb 'set' and resource 'absolute local workspace directory'. Distinguishes from sibling 'get_board_workspace'. No ambiguity.

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?

Explicitly says 'call this once at the beginning of work when the MCP process was not launched from the intended project directory', providing clear context. Implies when not to use.

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