Skip to main content
Glama
Sign In
workbuddy-subagent-bridge

workbuddy-subagent-bridge

by BenjaminNH
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

workbuddy_session_start

Start a WorkBuddy session to execute a prompt in a specified workspace, returning a task ID for status polling or a blocking report when waitForCompletion is enabled.

Instructions

Start a current-version WorkBuddy session. ACP mode returns a taskId immediately by default; poll status and request the report after completion. Set waitForCompletion=true when a blocking report is preferred.

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": {
      "cwd": "<cwd>",
      "prompt": "<prompt>"
    },
    "name": "workbuddy_session_start"
  }
}

Input Schema

NameRequiredDescriptionDefault
cwdYesExplicit existing workspace directory.
promptYes
backendNoauto prefers ACP and may use one-shot CLI fallback only before a prompt is submitted.auto
modelIdNoOptional model ID. Local validation fallback tries hy4-preview then deepseek-v4.1-flash when omitted.
permissionModeNoWorkBuddy permission mode. Default plan: read/analyze only. acceptEdits: auto-accept file edits. bypassPermissions: skip permission prompts (danger). fullAccess: skip all permission checks including dangerous commands (extreme danger). Other values pass through to the current WorkBuddy version.plan
waitForCompletionNoIf true, wait for the first prompt report; otherwise return the taskId immediately.
acceptanceCriteriaNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description must carry behavioral disclosure. It discloses the asynchronous default (taskId returned immediately, poll status for report) and the blocking alternative. However, it does not mention potential side effects, permission implications, or the fact that it initiates a potentially long-running process. The schema mentions permissionMode dangers but the description does not reinforce this.

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?

The description is two sentences with no filler. It front-loads the core purpose and then provides essential behavioral guidance. Every word 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 session-start tool with 7 params and no output schema, the description covers the key workflow aspects (immediate vs blocking, polling). It does not explain the return format beyond taskId, but that is implied. It also does not mention prerequisites like cwd existence, though that is in the schema. Overall, it is adequately complete for an agent to call it correctly.

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 71%, above the 50% threshold, so baseline is 3. The description adds workflow context (poll status, request report) but does not provide extra meaning for individual parameters beyond what the schema already documents. The schema already covers backend, permissionMode, and waitForCompletion well.

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 'Start' and the resource 'WorkBuddy session', making the purpose unambiguous. It also distinguishes itself from sibling tools like send/status/cancel by describing the session initiation behavior.

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?

It provides clear guidance on the two usage modes (default immediate return vs. waitForCompletion=true for blocking) and the associated polling workflow. However, it does not explicitly contrast with sibling tools (e.g., when to use send instead of start), so it lacks explicit exclusions or alternatives.

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