Skip to main content
Glama

Hub task timeline

hub_log
Read-only

View a task's merged, time-sorted event log to track state changes, worker progress, and inbox messages without loading the full task payload.

Instructions

One merged, time-sorted line per event on a task: state changes (the hub's commit subjects), worker PROGRESS lines and INBOX messages. A cheap way to see how a task is going without hub_show's full payload; for unattended watching prefer dispatch watch (README).

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

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A4.1/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 the description's job is to add context, and it does: it describes the exact shape of the response (one merged, time-sorted line per event) and its relative cost. It stops short of stating limits, truncation, or how much history is returned.

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 tightly packed sentences: output shape first, then cost/alternative routing. No filler, though the trailing README pointer is slightly awkward and the triple-hyphen appositive in sentence one is dense.

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?

With no output schema, the description must convey return content, and it does via the enumerated event categories and ordering. It is nearly complete for a simple one-parameter read tool; only ordering guarantees, volume limits, and empty-state behavior are unaddressed.

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?

The schema has 0% description coverage and the description never mentions the single `id` parameter. However, the sole parameter is the obvious task identifier matching the regex pattern in the schema, so the omission is tolerable rather than damaging; a note on task-id format or unknown-id behavior would have raised this.

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 concrete verb and resource: a merged, time-sorted timeline of events on a task, enumerating the three event kinds (state changes/commit subjects, PROGRESS, INBOX). It explicitly contrasts itself with hub_show's 'full payload', so an agent can distinguish it from a sibling without opening the schema.

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?

Gives a clear selection rule — use this as the cheap overview instead of hub_show, and use `dispatch watch` for unattended watching. The main weakness is that `dispatch watch` is not a sibling MCP tool and the guidance defers to a README, making the alternative less actionable inside the tool catalog.

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