Skip to main content
Glama

workbuddy_status

Check whether the authorized user's WorkBuddy PC local assistant is online to confirm availability before dispatching tasks or expecting local responses.

Instructions

Check whether the authorized user's WorkBuddy PC local assistant is online.

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/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 burden and does very little with it. It does not say whether this is a read-only probe, whether it can block or time out on an offline machine, whether it requires authorization to the remote host, or what an offline result looks like. For a no-parameter probe whose entire value is its boolean-ish result, that silence leaves the agent unable to interpret the outcome.

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, and the subject (local assistant online status) comes before any qualifications. It is tight, though so terse that the brevity is partly the cause of the behavioral gaps rather than a neutral virtue.

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?

For a zero-parameter status check with no annotations and no output schema, the definition covers the core question but omits how to read the result and when the check should be preferred over the other status tools. An agent can call it correctly but cannot fully plan around its failure mode or its return shape.

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, so there is nothing for the description to disambiguate and the baseline applies. The description correctly implies no inputs are needed to perform the check.

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 and resource: verifying whether the authorized user's WorkBuddy PC local assistant is online. That is clearly distinguishable from siblings like workbuddy_send_message or workbuddy_create_cloud_task. It stops short of contrasting with the similar-sounding clawbridge_status or codebuddy_health, so sibling differentiation is only partial.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use guidance, no stated preconditions, and no named alternative for checking connectivity of other agents. An agent can infer that this is a precondition probe before messaging, but that inference is not stated anywhere in the definition.

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