Skip to main content
Glama

Show one hub task

hub_show
Read-only

Retrieve the full record of a specific task by ID, including its spec, note, worker instructions, master answer, and the worker's report once completed.

Instructions

Full task record: spec, note, the instructions given to the worker, the master answer, and (once done) the worker's report.

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

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description does add one genuine behavioral detail beyond that: the worker's report is present only once the task is done, which tells the agent the record is time-dependent. It says nothing about what happens for an unknown or invalid id.

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?

One sentence, front-loaded with the key fact that this is the full record, followed by the list of what it contains. The field enumeration is long but each item adds real information to a tool that has no output schema.

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?

With no output schema, describing the return payload is exactly the description's job and it does so well. However, for a fetch tool it omits how the task is identified, what an invalid id yields, and how it relates to sibling hub tools, leaving gaps an agent must guess at.

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?

There is a single required id parameter with 0% schema description coverage, so the schema supplies only a regex pattern with no stated meaning. The description never names the parameter, but "Full task record" frames the call as being about one task, which lets an agent infer the id identifies a task.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The phrase "Full task record" plus the enumerated fields makes it reasonably clear this returns a single task's complete contents, but there is no verb and no mention of the identifying key, so an agent must infer from the title that this is a fetch-by-id operation. It gives no signal distinguishing it from siblings like hub_board or hub_log that may also return task data.

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, no mention of when this beats hub_board or hub_log, and no statement of a prerequisite such as needing a task id first. The parenthetical "(once done)" hints at timing but is about content availability, not tool selection.

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