Skip to main content
Glama

workbuddy_run

Runs a task in WorkBuddy by dispatching a prompt through the saved bridge conversation, honoring configured model, permissions, working directory, and timeout.

Instructions

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.

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

Input Schema

NameRequiredDescriptionDefault
cwdNo
promptYes
model_idNoauto
permission_modeNodeny
timeout_secondsNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and delivers real behavioral context: the bridge is not a sandbox, it never auto-grants permissions, and a timeout does not trigger an automatic retry. It does not describe error surfaces or what happens when a permission prompt is rejected mid-task, so it is not fully complete.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Sentences are individually tight, but the text is wrapped into fragments and mixes parameter semantics with behavioral warnings without clear grouping. Nothing is purely filler, yet the ordering makes the key 'what this tool does' statement compete with mode minutiae.

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?

An output schema exists, so return values need not be explained, and the description covers the main risk behaviors (no sandbox, no auto-grant, no retry). Remaining gaps are the undocumented cwd and timeout_seconds parameters, which leaves the definition slightly short for a 5-parameter 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 0%, so the description must compensate. It explains permission_mode's deny and allow_once values and that model_id 'auto' retains the conversation's model, which is genuinely useful, but cwd and timeout_seconds are left undocumented in both schema and description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Run a task in WorkBuddy') and adds the key scoping detail that it reuses the saved bridge conversation. It doesn't explicitly differentiate from siblings like workbuddy_continue or workbuddy_cancel, so it stops short of a 5.

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?

The permission-mode sentences imply when each mode applies (deny for read-only work, allow_once when the desktop user should authorize), but there is no explicit statement of when to pick this tool over workbuddy_continue or workbuddy_status. Usage must be inferred from the mode semantics rather than stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.