Skip to main content
Glama

send_worker_message

Send follow-up instructions to a running worker by typing a message into its tmux session, using project directory and feature ID to target the correct worker.

Instructions

Send a follow-up instruction or message to a running worker. The message will be typed into the worker's tmux session.

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": {
      "projectDir": "<projectDir>",
      "featureId": "<featureId>",
      "message": "<message>"
    },
    "name": "send_worker_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
messageYesThe message/instruction to send to the worker
featureIdYesID of the feature whose worker to message
projectDirYesAbsolute path to the project directory

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 does disclose the important mechanism that the message is typed into the worker's tmux session, which tells the agent this is a keystroke-level write, not an API call with a structured acknowledgement. It does not state whether delivery is confirmed, what happens if the worker is not running, or whether the message is queued.

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 short sentences with zero filler, and the core action is front-loaded before the delivery mechanism. Every clause contributes information an agent would otherwise have to guess.

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 three-required-parameter action tool with no output schema, the description covers what the tool does and how the message is delivered, which is the essential part. It omits what the call returns and how failures (missing session, worker exited) manifest, which leaves a meaningful gap for an agent deciding whether to rely on the result.

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 100%, so the schema already documents all three parameters and the baseline is 3. The description adds only the nuance that the message becomes literal terminal input, which slightly informs how to phrase the 'message' value but does not add routing or format details for featureId or projectDir.

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 specific verb and resource (send a message to a running worker) and scopes it as a 'follow-up instruction', which implicitly separates it from starting a worker. It stops short of naming a sibling like start_worker or check_worker, so the differentiation is left mostly to the word 'follow-up' and 'running'.

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 phrase 'running worker' implies this is for workers already in flight rather than for starting one, giving a workable usage context. However, there is no explicit when-not-to-use guidance, no mention of what to do if the worker has finished or is unresponsive, and no reference to alternatives.

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