Skip to main content
Glama
Sign In
AIWorkhub

AIWorkhub

by shrec
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

aiworkhub_task_list

Read-only

Lists task cards filtered by status and optional topic, returning the most recently updated first so you can review work in a flat, status-based view.

Instructions

List task cards by status and optional topic.

Use this for a flat card list by status; use aiworkhub_task_show for one card in full or aiworkhub_task_plan_snapshot for the dependency DAG.

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": "aiworkhub_task_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of cards to list, most recently updated first; default 80, values below 1 are treated as 1.
topicNoOnly list cards with exactly this topic; omit for all topics.
statusNoStatus to list, e.g. pending, processing, blocked, done or all for every status; default pending.pending

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.12.67
    • addedInput schema / properties / limit / description
      Added value: +"Maximum number of cards to list, most recently updated first; default 80, values below 1 are treated as 1."
    • addedInput schema / properties / status / description
      Added value: +"Status to list, e.g. pending, processing, blocked, done or all for every status; default pending."
    • addedInput schema / properties / topic / description
      Added value: +"Only list cards with exactly this topic; omit for all topics."
  2. First observedv0.1.0

TDQS

A4.2/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 adds the shape of the result ('flat card list') as opposed to a full card or a DAG, which is genuine context, but it says nothing about ordering, truncation behavior, or empty results. Adequate rather than rich given the annotation coverage.

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, zero filler. The primary use case comes first and the disambiguation to siblings follows, which is the right order for an agent deciding whether to call this tool.

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 annotations covering safety, an output schema covering return values, and fully described parameters, the description's remaining job is routing, which it does well. It stops short of noting default status='pending' or the limit cap, but those live in the schema and the agent will see them there.

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?

Schema description coverage is 100%, and each parameter already documents its default, ordering ('most recently updated first'), and the 'all' sentinel for status. The description only restates that status and topic are the filters, adding no syntax or edge-case meaning beyond the schema. Baseline 3 is appropriate.

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 specific verb and resource ('List task cards') plus the two axes it operates on ('by status and optional topic'). It also explicitly distinguishes itself from aiworkhub_task_show and aiworkhub_task_plan_snapshot, so an agent can pick it without opening any schema.

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?

Names two concrete alternatives and the condition that selects each: aiworkhub_task_show for a single full card, aiworkhub_task_plan_snapshot for the dependency DAG. The default case (flat card list by status) is front-loaded, leaving nothing to inference.

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

Deploy Server

Other Tools