Skip to main content
Glama

List hub tasks

hub_board
Read-only

List every task in the dispatch hub with its current state, assignee, and latest note so agents can monitor and triage queued, running, completed, or failed work.

Instructions

All tasks in the dispatch hub with state, assignee and latest note. States: queued, assigned, running, done, need-info, failed, accepted, rejected, cancelled.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "hub_board"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

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 already declare readOnlyHint=true and openWorldHint=false, so safety is covered. Beyond that, the description usefully discloses what each record exposes and enumerates the nine possible state values, which is genuinely new context not present in any structured field since there is no output schema. It stops short of stating ordering, result limits, or whether the board is truncation-prone.

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 sentences, front-loaded with the scope and return fields, then the state vocabulary. Every clause earns its place and there is no filler or restatement of the title.

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 zero-parameter read tool with no output schema, the description carries the return-shape burden well by naming the three exposed fields and the full state set. Minor gap: it never says how results are ordered or whether there is a cap on the number of tasks returned.

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?

The tool takes zero parameters and the schema is an empty object, so there is nothing for the description to disambiguate. The baseline of 4 applies; no parameter-level meaning is missing because no parameters exist.

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 names the concrete resource (all tasks in the dispatch hub) and the fields each entry carries (state, assignee, latest note), so an agent knows this is a full listing. It does not explicitly contrast itself with hub_show or hub_wait, leaving the single-task vs. full-board distinction to inference.

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

Usage Guidelines2/5

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

There is no when-to-use guidance at all: nothing says to call this before hub_show to discover task IDs, nor that it takes no filters. The only implicit signal is the word 'All', which hints the call is unfiltered, but the agent must infer the rest from the sibling names.

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