Skip to main content
Glama
bzdOS

hubd

by bzdOS
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
JavaScript
Local

hub_brief

Delivers a cross-project status brief: tasks by deadline, journal activity, stale cards, claims, queue depths, owner-waiting items, and top lint/audit findings.

Instructions

Morning brief across all projects: open tasks (deadlines first), journal since N hours, stale cards, cards whose digest trails their own journal (staleDigests — the misleading kind of stale), active claims, per-role queue depth with last-seen agent (broadcast roles are flagged fanout instead of a depth — their cursors are per-reader), and a buttons rollup ("N buttons waiting, oldest X days" — pending items in a human-owner queue, see HUB/owner-roles.json). Two things wait on the owner and they are NOT the same: buttonItems = each unanswered package in an owner queue (age, sender, subject); ownerWaiting = open tasks only the owner can move, with age and how far past deadline — invisible in every "what can I start" list because the answer there is "not this". review carries the top few hub_lint + hub_audit findings, one per kind, each quoting the rule it enforces with the date that rule was written: the audit rides on this call instead of waiting to be remembered. It reports only — nothing is filed without an explicit hub_audit({apply:true}) carrying somebody's name.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fullNoreturn everything, uncapped. By default long lists are trimmed to fit an agent context and what was left out is reported in `truncated`.
hoursNojournal window, default 48
staleDaysNocard considered stale after N days, default 7
reviewLimitNohow many finding KINDS to inline, default 3; 0 turns the review block off

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.9.12
    • addedInput schema / properties / reviewLimit
      Added value: +{
+  "description": "how many finding KINDS to inline, default 3; 0 turns the review block off",
+  "type": "integer"
+}
  2. Changed1 schema field changedv0.9.0
    • addedInput schema / properties / full
      Added value: +{
+  "description": "return everything, uncapped. By default long lists are trimmed to fit an agent context and what was left out is reported in `truncated`.",
+  "type": "boolean"
+}
  3. First observedv0.1.6

TDQS

A4.4/5.0
Behavior5/5

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

With no annotations provided, the description carries the full behavioral burden and does so thoroughly. It explicitly states 'It reports only', clarifies that nothing is filed without an explicit hub_audit apply, explains that review embeds hub_lint and hub_audit findings, and disambiguates subtle behaviors like staleDigests and per-reader cursors for broadcast roles. This fully compensates for the missing annotations.

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?

The description is front-loaded with the core purpose and a list of report contents, then adds necessary disambiguation of buttonItems versus ownerWaiting and the audit boundary. It is dense and somewhat run-on, but every sentence provides useful behavioral or conceptual detail rather than filler.

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

Completeness5/5

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

For a read-only brief tool with no output schema and no annotations, the description is remarkably complete: it enumerates every major section of the result, explains truncation behavior, references configuration for owner queues, and clearly states the side-effect policy. An agent has enough context to invoke the tool and interpret the returned report without hidden surprises.

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?

All four parameters are already described in the input schema with clear meanings (full, hours, staleDays, reviewLimit), so the baseline is 3. The description reinforces concepts like reviewLimit being about finding kinds and full controlling truncation, but it does not add significant meaning beyond what the schema already provides.

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 clearly identifies a concrete resource and behavior: a morning brief aggregating open tasks, journal entries, stale cards, claims, queue depth, buttons, and review findings across all projects. It is specific enough to be understood without opening the schema, though it does not explicitly name or contrast sibling report tools such as hub_report, hub_status, or hub_agenda.

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?

The description gives strong when/when-not guidance: it is a read-only morning rollup, and any intended filing or mutation requires an explicit hub_audit({apply:true}) carrying somebody's name. It also explains that the audit/review rides along on this call instead of waiting to be remembered, and distinguishes ownerWaiting from 'what can I start' lists, which helps the agent route correctly.

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

Install Server

Other Tools