AIWorkhub

by shrec

Overview Schema Source Related Servers Discussions Admin

Python

Hybrid

aiworkhub_dashboard_needfix_transition

USER WRITE: apply one confirmed lifecycle status transition to a NeedFix item.

Instructions

USER WRITE: apply one confirmed lifecycle status transition to a NeedFix item.

Use this to triage, accept, reject, defer, mark duplicate, mark task_planned, resolve, or recover a conversion claim; use aiworkhub_dashboard_needfix_archive, aiworkhub_dashboard_needfix_restore, or aiworkhub_dashboard_needfix_convert_commit for archive, restore, or task creation. Requires confirm=True, persists the state transition and audit event in the NeedFix store, and returns a transition receipt.

Input Schema

Name	Required	Description
`action`	Yes	str transition action: triage, accept, reject, duplicate, defer, task_planned, resolve, resolve_verified, or recover_conversion_claim.
`reason`	No	str note or rationale (default "", up to 1000 chars; required for recover_conversion_claim).
`confirm`	No	bool (default False); must be True to execute the transition.
`needfix_id`	Yes	str canonical NeedFix identifier to transition.
`promote_to`	No	str optional chained target (default ""; only "accepted" with action="triage" is allowed).
`include_item`	No	bool (default False); True adds full detail fields to item.
`readiness_score`	No	optional int score for triage or accept (default None).
`duplicate_parent_id`	No	str parent NeedFix ID when action is duplicate (default "").

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedv0.12.62Oct 23, 2026

addedInput schema / properties / action / description

Added value: +"str transition action: triage, accept, reject, duplicate, defer, task_planned, resolve, resolve_verified, or recover_conversion_claim."

addedInput schema / properties / confirm / description

Added value: +"bool (default False); must be True to execute the transition."

addedInput schema / properties / duplicate_parent_id / description

Added value: +"str parent NeedFix ID when action is duplicate (default \"\")."

addedInput schema / properties / include_item / description

Added value: +"bool (default False); True adds full detail fields to item."

addedInput schema / properties / needfix_id / description

Added value: +"str canonical NeedFix identifier to transition."

addedInput schema / properties / promote_to / description

Added value: +"str optional chained target (default \"\"; only \"accepted\" with action=\"triage\" is allowed)."

addedInput schema / properties / readiness_score / description

Added value: +"optional int score for triage or accept (default None)."

addedInput schema / properties / reason / description

Added value: +"str note or rationale (default \"\", up to 1000 chars; required for recover_conversion_claim)."

First observedv0.1.0Oct 20, 2026

TDQS

A4.5/5.0

Behavior4/5

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

No annotations are present, so the description carries the full burden. It discloses that this is a USER WRITE that persists a state transition and audit event, requires confirm=True, and returns a transition receipt. It does not detail error conditions, reversibility, or rate limits, but for a write tool this is a strong disclosure.

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 with zero waste: the first sentence states the purpose and mutation nature, the second covers usage, alternatives, and key behaviors. The critical 'USER WRITE' and confirm requirement are front-loaded.

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?

Output schema exists, so return values are already documented. Given the 8-parameter complexity, the description covers purpose, usage alternatives, confirm requirement, persistence, audit event, and receipt. Nothing an agent needs to call 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%, so the schema already documents all 8 parameters including the action enum and confirm flag. The description mentions the action list and confirm requirement, but adds no syntax or behavior beyond what the schema provides. 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+resource ('apply one confirmed lifecycle status transition to a NeedFix item') and explicitly names sibling tools for other operations (archive, restore, convert_commit). An agent can distinguish this from all other NeedFix tools 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 Guidelines5/5

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

Explicitly lists when to use this tool (triage, accept, reject, defer, mark duplicate, mark task_planned, resolve, recover conversion claim) and when to use alternatives (archive, restore, convert_commit). Also states the confirm=True requirement, leaving no ambiguity about invocation conditions.

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

Deploy Server