Skip to main content
Glama
Sign In
AIWorkhub

AIWorkhub

by shrec
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

aiworkhub_dashboard_needfix_transition

Applies one confirmed lifecycle transition to a NeedFix item or up to 25 at once for triage, accept, reject, defer, duplicate, resolve, or recovery, returning a per-item transition receipt.

Instructions

USER WRITE: apply one confirmed lifecycle transition to one NeedFix or up to 25.

Use this to triage, accept, reject, defer, mark duplicate or task_planned, resolve, or recover a conversion claim; archive, restore and convert have their own tools. Requires confirm=True and returns a transition receipt.

A task-less fix closes with action=resolve_verified (readiness_score=100, evidence, evidence_refs) or a Resolves: NF-YYYY-NNNNN commit trailer. With needfix_ids the reply is {results, succeeded, failed} and a refused row leaves the others applied.

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

Input Schema

NameRequiredDescriptionDefault
actionNotriage, accept, reject, duplicate, defer, task_planned, resolve, resolve_verified, or recover_conversion_claim.
reasonNonote, up to 1000 chars; required for recover_conversion_claim.
confirmNomust be True to execute.
evidenceNomerge-patch object; resolve_verified only.
needfix_idNoID to transition; exactly one of this and needfix_ids.
promote_toNooptional; only "accepted" with action=triage.
needfix_idsNoup to 25 distinct IDs, one result per id.
include_itemNoTrue adds full item detail.
evidence_refsNorefs to add; resolve_verified only.
readiness_scoreNooptional score for triage or accept.
duplicate_parent_idNoparent ID for action=duplicate.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.12.98
    • addedInput schema / properties / evidence
      Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "merge-patch object; resolve_verified only.",
+  "title": "Evidence"
+}
    • addedInput schema / properties / evidence_refs
      Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "refs to add; resolve_verified only.",
+  "title": "Evidence Refs"
+}
  2. Changed5 schema fields changedv0.12.96
    • addedInput schema / properties / action / default
      Added value: +""
    • addedInput schema / properties / needfix_id / default
      Added value: +""
    • changedInput schema / properties / needfix_id / description
      Previous value: -"NeedFix ID to transition."New value: +"ID to transition; exactly one of this and needfix_ids."
    • addedInput schema / properties / needfix_ids
      Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "up to 25 distinct IDs, one result per id.",
+  "title": "Needfix Ids"
+}
    • removedInput schema / required
      Removed value: -[
-  "needfix_id",
-  "action"
-]
  3. Changed8 schema fields changedv0.12.85
    • changedInput schema / properties / action / description
      Previous value: -"str transition action: triage, accept, reject, duplicate, defer, task_planned, resolve, resolve_verified, or recover_conversion_claim."New value: +"triage, accept, reject, duplicate, defer, task_planned, resolve, resolve_verified, or recover_conversion_claim."
    • changedInput schema / properties / confirm / description
      Previous value: -"bool (default False); must be True to execute the transition."New value: +"must be True to execute."
    • changedInput schema / properties / duplicate_parent_id / description
      Previous value: -"str parent NeedFix ID when action is duplicate (default \"\")."New value: +"parent ID for action=duplicate."
    • changedInput schema / properties / include_item / description
      Previous value: -"bool (default False); True adds full detail fields to item."New value: +"True adds full item detail."
    • changedInput schema / properties / needfix_id / description
      Previous value: -"str canonical NeedFix identifier to transition."New value: +"NeedFix ID to transition."
    • changedInput schema / properties / promote_to / description
      Previous value: -"str optional chained target (default \"\"; only \"accepted\" with action=\"triage\" is allowed)."New value: +"optional; only \"accepted\" with action=triage."
    • changedInput schema / properties / readiness_score / description
      Previous value: -"optional int score for triage or accept (default None)."New value: +"optional score for triage or accept."
    • changedInput schema / properties / reason / description
      Previous value: -"str note or rationale (default \"\", up to 1000 chars; required for recover_conversion_claim)."New value: +"note, up to 1000 chars; required for recover_conversion_claim."
  4. Changed8 schema fields changedv0.12.62
    • 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)."
  5. First observedv0.1.0

TDQS

A4.5/5.0
Behavior5/5

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

Adds substantial context beyond the annotations: a confirm gate, a transition receipt return, and critically the partial-failure semantics ('a refused row leaves the others applied') plus the required closure paths for task-less fixes (resolve_verified with readiness_score/evidence, or a `Resolves:` commit trailer). This is exactly the mutation/commit-trailer behavior an agent cannot infer from readOnlyHint=false and destructiveHint=false.

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?

Front-loaded with the write classification and scope, then alternatives, then batch/closure semantics. Sentences are dense but each carries information; the commit-trailer detail is terse enough to be worth its space, though the paragraph structure is compressed into a wall of clauses.

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?

For an 11-parameter mutation tool with an output schema present, the description covers the gate, the action surface, batch partial failure and closure requirements. Minor gaps remain around per-action prerequisites and the promote_to/duplicate paths, which the schema text carries instead.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning on top: confirm must be True to execute, evidence/evidence_refs apply only to resolve_verified, and needfix_ids yields a {results, succeeded, failed} reply. Other parameters (promote_to, duplicate_parent_id, include_item) are left entirely to the schema.

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 ('apply one confirmed lifecycle transition to one NeedFix or up to 25') and immediately scopes it against siblings by noting archive, restore and convert have their own tools. An agent can distinguish this from needfix_archive or needfix_convert without opening a 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 lists the actions it covers (triage, accept, reject, defer, duplicate, task_planned, resolve, recover_conversion_claim) and excludes archive/restore/convert by pointing at dedicated tools, plus the confirm=True prerequisite. It does not say which action to pick in a given situation, leaving that to the schema's action descriptions.

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