Skip to main content
Glama

Override a hub task's assignment

hub_assign
Idempotent

Manually assign a queued or already assigned task to a specific worker, bypassing the scheduler. Use it to route work to a chosen worker id from the hub board or roster.

Instructions

Assign a queued (or assigned) task to a specific worker yourself, bypassing the scheduler. See hub_board / the workers roster for ids.

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>",
      "worker": "<worker>"
    },
    "name": "hub_assign"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
reasonNo
workerYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare idempotentHint=true, destructiveHint=false and readOnlyHint=false, so safety is covered. The description adds the meaningful behavioral note that this bypasses the scheduler — an override, not a normal queue flow. It does not say what happens to the previous assignee, whether the worker is notified, or what the call returns.

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?

Two short sentences, front-loaded with the action and its override nature, followed by an id-lookup pointer. No wasted wording, though the id pointer is terse enough to be slightly cryptic.

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 mutation with no output schema and zero schema documentation, the description is thin on effect: it does not describe the result, side effects on the prior assignee, or the purpose of 'reason'. The core action and eligibility are present, but an agent still has gaps before calling it confidently.

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%, so the description must carry parameter meaning, and it largely doesn't. It only tells where to find valid id/worker values (hub_board / workers roster); the 'reason' parameter is never mentioned and the id pattern is left entirely to the schema.

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 uses a specific verb and resource ('Assign a ... task to a specific worker') and adds the key qualifier that it bypasses the scheduler, which distinguishes it from automated dispatch. It is clear what the tool does, though it doesn't directly contrast with siblings like hub_requeue or hub_cancel.

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?

It states the eligible task states ('queued (or assigned)') and the manual-override context, and points to hub_board / the workers roster for ids. However, it gives no explicit when-not guidance and never names an alternative tool for the automated path, leaving the choice to inference.

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