Skip to main content
Glama

workbuddy_continue

Continue an existing WorkBuddy conversation without clearing its context, letting you resume a saved session and send a new prompt while retaining prior conversation state.

Instructions

Continue a specific existing WorkBuddy conversation without clearing context.

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

Input Schema

NameRequiredDescriptionDefault
cwdNo
promptYes
model_idNoauto
session_idYes
permission_modeNodeny
timeout_secondsNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full burden, and it discloses only one behavioral trait: conversation context is preserved rather than cleared. It says nothing about the meaning or effect of permission_mode (default "deny"), blocking/timeout behavior, what happens if session_id is unknown, or whether the call can fail destructively.

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

Conciseness4/5

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

A single front-loaded sentence with no filler; the key constraint (context is not cleared) is placed immediately. Brevity here is efficient, though it borders on under-specification given the parameter surface.

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

Completeness2/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, but for a six-parameter session tool with zero annotation coverage the description is far too thin. Critical operational details—permission_mode semantics and default, timeout behavior, and session validity handling—are entirely absent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across six parameters, so the description must compensate and largely does not. Only session_id is obliquely implied by "a specific existing conversation"; prompt, model_id, cwd, permission_mode, and timeout_seconds are given no meaning at all.

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?

The description states a specific verb ("Continue") and resource ("existing WorkBuddy conversation") and the qualifier "existing" implicitly distinguishes it from a fresh-run tool like workbuddy_run. It does not name or contrast any sibling explicitly, so it falls 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?

"Continue a specific existing ... conversation" implies the prerequisite of an already-created session, and "without clearing context" hints at the condition that selects this over starting anew. However, there is no explicit when-to-use/when-not guidance and no named alternative.

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