Skip to main content
Glama

Message a hub task's worker

hub_tell

Append a short one-line message to a task's inbox so workers see it on their next hub check. Use for nudges and clarifications that need no state change.

Instructions

Append a short message (collapsed to one line, max 300 chars) to the task's inbox. The worker sees INBOX lines on its next hub say/inbox/next and is expected to follow them. Use for nudges and clarifications that do not need a state change (unlike hub_answer, which replies to need-info).

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": {
      "id": "<id>",
      "text": "<text>"
    },
    "name": "hub_tell"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
textYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A4.6/5.0
Behavior4/5

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

Annotations only declare a non-read-only, non-destructive, non-idempotent mutation; the description adds the non-obvious delivery model (the worker sees INBOX lines on its next hub say/inbox/next and is expected to follow them), meaning the message is queued rather than delivered immediately. It also discloses that text is collapsed to one line and capped at 300 chars, which the annotations do not cover. Minor gaps remain around failure behavior and whether messages are lost if the task never runs again.

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?

Three tight sentences, no filler: mechanism first, delivery model second, routing guidance third. Every sentence adds a fact an agent could not get from the schema or annotations.

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

Completeness4/5

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

For a two-parameter mutation with annotations and no output schema, the description covers what it writes, how much, how it is delivered, and when to prefer the alternative. Only error/edge behavior (invalid or completed task id) is unaddressed.

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?

Schema description coverage is 0%, so the description must carry the parameters, and it does add the key constraint the schema omits: text is collapsed to one line and limited to 300 chars (the schema only sets minLength 1). The id parameter is only implicitly explained as 'the task's' inbox, with no note on where to obtain a task id or its T########-######-xx format.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: 'Append a short message... to the task's inbox.' It also names the sibling it is not (hub_answer) with the distinguishing condition, so an agent can separate the two without opening either schema.

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

Usage Guidelines5/5

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

Explicit when-to-use ('nudges and clarifications that do not need a state change') plus an explicit exclusion routing need-info replies to hub_answer. Nothing is left to inference about which of the two messaging tools to pick.

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