Skip to main content
Glama

workbuddy_send_message

Send a plain-text instruction to the WorkBuddy PC local assistant to trigger authorized local file or tool actions and retrieve results.

Instructions

Send a plain-text instruction to the WorkBuddy PC local assistant. This may cause WorkBuddy to use local files or tools, so keep the instruction within the user's authorized scope.

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": {
      "content": "<content>"
    },
    "name": "workbuddy_send_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
contentYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/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. It usefully discloses that WorkBuddy may act on local files or tools and reminds the caller to stay within authorized scope, which is real side-effect context. It omits whether the call returns a reply, queues asynchronously, or how failures surface.

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?

Two tight sentences with no padding, and the core action is stated first with the caveat second. Every clause carries information.

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 one-parameter tool with no output schema, purpose plus side-effect warning covers most needs. What is missing is the interaction model — whether a reply comes back immediately or must be fetched via workbuddy_wait_for_reply/workbuddy_message_history — which materially affects correct invocation.

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% for the single parameter, so the description must compensate. 'Plain-text instruction' and 'keep the instruction within the user's authorized scope' give some semantic framing for `content`, but nothing on length, structure, or whether embedded commands/paths are interpreted.

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 gives a concrete verb and target: send a plain-text instruction to the WorkBuddy PC local assistant. That distinguishes it from history/status siblings at the PC-assistant level, though it does not explicitly name alternatives such as cloud-task creation tools.

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?

Usage is implied by 'instruction to the WorkBuddy PC local assistant' — i.e., delegate an action to the local machine rather than query state — and the scope caveat shapes what to send. There is no explicit when-not-to-use guidance or reference to the sibling tools (wait_for_reply, message_history) that an agent would need to pick the right call.

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