Skip to main content
Glama
Sign In
AIWorkhub

AIWorkhub

by shrec
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

aiworkhub_agent_list_processes

Read-only

Summarize recent worker processes across all tasks in read-only mode, including state counts and timestamps; use detail='full' to inspect complete legacy records.

Instructions

READ-ONLY: summarize latest processes; use detail='full' for legacy records.

Use this for the newest worker processes across all tasks; use aiworkhub_agent_task_status for one launched request in detail.

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

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of latest processes to read, integer 1-1000; default 100, any other value is refused with invalid_limit.
detailNosummary (default) returns counts by state and terminal substatus plus newest/oldest timestamps; full returns the complete legacy process records.summary

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.12.67
    • addedInput schema / properties / detail / description
      Added value: +"summary (default) returns counts by state and terminal substatus plus newest/oldest timestamps; full returns the complete legacy process records."
    • addedInput schema / properties / limit / description
      Added value: +"Number of latest processes to read, integer 1-1000; default 100, any other value is refused with invalid_limit."
  2. First observedv0.1.0

TDQS

A4/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 'READ-ONLY' prefix adds nothing. The only extra behavioral signal is that detail='full' reaches legacy records, which is useful but thin; there is no mention of ordering guarantees, default scope, or error behavior beyond what the schema already documents.

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 short, front-loaded sentences with no filler; the routing information comes first and the sibling pointer second. The 'READ-ONLY:' label duplicates the annotation and is the only wasted token.

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?

An output schema exists, both parameters are fully documented in the schema, and annotations carry the safety profile, so the description only needs to establish scope and routing — which it does. Nothing required to call it correctly is missing.

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 coverage is 100%, and the schema itself explains the limit range, the invalid_limit refusal, and what summary vs full return. The description's 'use detail="full" for legacy records' largely restates the schema's 'complete legacy process records', so baseline 3 is appropriate.

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 states a specific verb and resource ('summarize latest processes') and scopes it ('newest worker processes across all tasks'), which separates it from the per-request sibling. It stops short of 5 because 'processes' is never concretely defined beyond a passing reference to 'legacy records'.

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?

It explicitly routes the agent: use this tool for the newest worker processes across all tasks, and use aiworkhub_agent_task_status for one launched request in detail. Both the when-to-use and the alternative are named with the selecting condition.

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