Skip to main content
Glama
Sign In
AIWorkhub

AIWorkhub

by shrec
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

aiworkhub_task_stale_recovery_recommend

Read-only

Recommends recovery actions for stale processing tasks or triages blocked cards by scope, producing read-only guidance without changing tasks or killing processes.

Instructions

READ-ONLY: recommend recovery actions for stale processing tasks or blocked cards.

scope="processing" (default) covers stale processing tasks. scope="blocked" triages the blocked-card queue: one recommendation per card, limit bounds the cards read (see bounds.truncated) and sample the rows listed per group. Produces recommendations only. It never calls taskctl write commands and never kills a process.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum cards to read, default 200; with scope=blocked it is clamped to at least 1 and bounds.truncated reports when more cards matched.
scopeNoprocessing (default) recommends actions for stale processing tasks; blocked triages blocked cards; anything else is refused with unknown_scope.processing
topicNoOnly consider cards with this topic; omit for all topics.
sampleNoRows listed per recommendation group when scope=blocked, default 10; unused for scope=processing.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.12.67
    • addedInput schema / properties / limit / description
      Added value: +"Maximum cards to read, default 200; with scope=blocked it is clamped to at least 1 and bounds.truncated reports when more cards matched."
    • addedInput schema / properties / sample / description
      Added value: +"Rows listed per recommendation group when scope=blocked, default 10; unused for scope=processing."
    • addedInput schema / properties / scope / description
      Added value: +"processing (default) recommends actions for stale processing tasks; blocked triages blocked cards; anything else is refused with unknown_scope."
    • addedInput schema / properties / topic / description
      Added value: +"Only consider cards with this topic; omit for all topics."
  2. Changed2 schema fields changedv0.12.64
    • addedInput schema / properties / sample
      Added value: +{
+  "default": 10,
+  "title": "Sample",
+  "type": "integer"
+}
    • addedInput schema / properties / scope
      Added value: +{
+  "default": "processing",
+  "title": "Scope",
+  "type": "string"
+}
  3. First observedv0.1.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; the description adds real value by reinforcing that it produces recommendations only, never calls taskctl write commands, and never kills a process. It also notes bounds.truncated for the blocked scope, helping the agent interpret results beyond what annotations provide.

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 READ-ONLY safety banner is front-loaded and the rest is compact, with each sentence covering scope behavior or safety. Slightly dense with backticked references, but no wasted prose.

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 an output schema present and full schema coverage, the description doesn't need to explain return values, and it adequately covers the two scopes and safety profile. An agent has what it needs to invoke correctly, minor gaps in sibling routing aside.

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%, so the schema already documents all four parameters thoroughly. The description adds only marginal context, largely restating limit/sample scoping that is already in the parameter descriptions. 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 (recommend) and resource (recovery actions for stale processing tasks / blocked cards) and clearly marks it as read-only advisory output. It distinguishes the two operating modes up front, so an agent understands what the tool produces 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?

Explicitly explains when each scope applies (processing for stale tasks, blocked for card triage) and how limit/sample behave per scope. It does not name sibling alternatives like the reconcile/recover tools, but it gives clear contextual guidance for correct invocation.

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