Skip to main content
Glama

Answer a hub task's question

hub_answer

Reply to a task awaiting information and route the answer back to the same worker so it can continue its session.

Instructions

Reply to a task in need-info; it goes back to the same worker (a ZCode worker continues its session with the answer).

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_answer"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
textYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations declare a non-read-only, non-destructive, non-idempotent write. The description adds genuinely new behavioral context: the answer is routed back to the same worker, and for a ZCode worker it resumes that worker's existing session rather than starting fresh. It omits what happens on success (does the task leave need-info?), what occurs if the task is not in need-info, and permission requirements.

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 front-loaded sentence that puts the precondition first and the routing behavior second. Every clause earns its place, with no restatement of the tool name or title.

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 two-parameter write tool with no output schema, the description covers the essential 'where does this go' question but leaves the agent guessing on identifier format, answer content expectations, and what a failed reply looks like. Adequate to attempt the call, not enough to call it confidently in edge cases.

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

Parameters2/5

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

Schema description coverage is 0% for both parameters, so the description carries the full burden and largely fails it. It only obliquely maps 'text' to the answer; it never explains that 'id' is a task identifier with a strict T########-######-xx format, nor what the text body should contain (plain answer vs. instructions), nor any length/format expectations.

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 (reply) and a specific preconditioned resource (a task in need-info), so the agent knows this delivers an answer to a task rather than posting a new message. It does not directly contrast itself with outbound siblings such as hub_post or hub_tell, so differentiation relies on the need-info state rather than explicit naming.

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

Usage Guidelines4/5

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

The trigger condition is explicit: use this when a task is in need-info. That is enough to route the agent correctly against general-purpose posting tools, but there are no exclusions (e.g., what to use when the task is not in need-info) and no alternative named.

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