Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
WORKBUDDY_BRIDGE_HOMENo会话状态和默认任务目录,可用于隔离多个桥接实例%LOCALAPPDATA%\openbot-workbuddy-bridge
WORKBUDDY_BRIDGE_PORTNo本机调试端口,必须与 WorkBuddy 启动参数一致19389

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
workbuddy_statusB

Check the existing WorkBuddy desktop debug endpoint; does not call a model.

workbuddy_runA

Run a task in WorkBuddy, reusing the saved bridge conversation.

deny requests read-only behavior and rejects interactive permission prompts. It is not a sandbox. allow_once leaves authorization to the WorkBuddy desktop UI; this bridge never automatically grants permissions. Model auto retains the conversation's WorkBuddy model. A timeout never triggers an automatic retry.

workbuddy_continueC

Continue a specific existing WorkBuddy conversation without clearing context.

workbuddy_cancelB

Request cancellation of a WorkBuddy conversation; does not undo past actions.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.5/5.0

Scored across 4 tools

Disambiguation4/5

The tools map to distinct lifecycle actions: status, run, continue, and cancel. run and continue could be confused because both can reuse a saved conversation, but the descriptions clarify that continue targets a specific existing conversation while run executes a task.

Naming Consistency5/5

All tools use a consistent snake_case workbuddy_verb pattern. The names are predictable and immediately indicate the action.

Tool Count5/5

Four tools are well-scoped for a narrow desktop bridge: check status, run, continue, and cancel. There is no obvious bloat, and each tool has a clear role.

Completeness4/5

The surface covers the core lifecycle of checking status, running, continuing, and cancelling a WorkBuddy conversation. A minor gap is the lack of an explicit tool to list or discover existing conversations, which may be needed before continue can be used confidently.