Skip to main content
Glama
Sign In
AIWorkhub

AIWorkhub

by shrec
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

needfix_reopen_superseded_task_link

Idempotent

Reopen a NeedFix when its exact linked task was superseded; record a required reason in the audit event. Manager-only action to restore the NeedFix workflow.

Instructions

Manager-only: reopen a NeedFix whose exact linked task was superseded.

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": {
      "needfix_id": "<needfix_id>",
      "reason": "<reason>"
    },
    "name": "needfix_reopen_superseded_task_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonYesRequired non-blank explanation, at most 4096 bytes, recorded in the audit event.
needfix_idYesNeedFix id, e.g. NF-2026-01447.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.12.67
    • addedInput schema / properties / needfix_id / description
      Added value: +"NeedFix id, e.g. NF-2026-01447."
    • addedInput schema / properties / reason / description
      Added value: +"Required non-blank explanation, at most 4096 bytes, recorded in the audit event."
  2. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already cover the safety profile (idempotent, non-destructive, mutating). The description adds the manager-only permission and the specific precondition (exact linked task superseded), but does not explain what reopening entails or what side effects occur, so it adds moderate value beyond annotations.

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?

The description is a single, front-loaded sentence with zero waste. Every word contributes to stating the permission and precondition.

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?

Given the mutation nature and specific precondition, the description covers the key permission and trigger. However, it omits details such as what reopening changes (e.g., NeedFix status, task link state) and any return behavior, leaving some contextual gaps that annotations and schema only partially fill.

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 both parameters are fully documented in the schema. The description does not add further meaning to needfix_id or reason 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 states a specific verb (reopen), resource (NeedFix), and precondition (exact linked task was superseded), making the purpose clear. It doesn't explicitly name sibling tools like needfix_restore or needfix_link_existing_task, but the condition itself differentiates it.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage when a NeedFix's exact linked task was superseded and notes it is manager-only. It does not explicitly compare to alternatives or state when not to use it, so guidance is implied rather than explicit.

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