Skip to main content
Glama

workbuddy_status

Checks whether the WorkBuddy desktop debug endpoint is reachable and responding, without calling a model. Use it to confirm bridge connectivity before dispatching prompts or reading results.

Instructions

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

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "workbuddy_status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden. It adds one useful behavioral fact (no model call) but says nothing about permission requirements, failure/timeout behavior, or whether it is a safe read-only probe — significant gaps for a tool with zero annotation coverage.

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?

A single imperative sentence with the scope constraint front-loaded and no filler; the negative clause earns its place by ruling out model invocation.

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

Completeness3/5

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

With zero parameters and an output schema present, the return values need not be described, and the call signature is trivially complete. What remains unexplained is the operational meaning of "check" — what a failure or an unreachable endpoint looks like, and whether it is non-destructive — which is thin for a diagnostic tool.

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

Parameters4/5

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

The tool takes zero parameters and the description names none, so there is no parameter semantics to explain; baseline 4 applies. The description neither confuses nor overstates the (empty) input surface.

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 ("check") and resource ("WorkBuddy desktop debug endpoint"), and the clause "does not call a model" distinguishes it from the model-invoking sibling workbuddy_run. Minor ambiguity: "check the existing ... endpoint" could mean probe for existence or query its status.

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 "does not call a model" qualifier implies the intended context (a cheap status probe before or instead of a model-backed run), but it never states when to call this versus workbuddy_run or the other siblings, nor any prerequisites.

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