Skip to main content
Glama
shrec

AIWorkhub

by shrec
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

aiworkhub_dashboard_needfix_archive

USER WRITE: archive one non-converting NeedFix item without deleting its stored record.

Instructions

USER WRITE: archive one non-converting NeedFix item without deleting its stored record.

Use this to move an inactive or obsolete NeedFix row out of the active inbox; use aiworkhub_dashboard_needfix_restore to return an archived row to an active status, or aiworkhub_dashboard_needfix_purge to permanently delete an archived row. Requires confirm=True, refuses rows currently in converting status, sets status to archived with an audit event in the NeedFix store, and returns the updated item.

Input Schema

NameRequiredDescriptionDefault
reasonNostr optional archive rationale (default "", truncated to 1000 chars) recorded in the audit event.
confirmNobool (default False); must be True to archive the NeedFix item.
needfix_idYesstr canonical NeedFix identifier to archive.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.12.62
    • addedInput schema / properties / confirm / description
      Added value: +"bool (default False); must be True to archive the NeedFix item."
    • addedInput schema / properties / needfix_id / description
      Added value: +"str canonical NeedFix identifier to archive."
    • addedInput schema / properties / reason / description
      Added value: +"str optional archive rationale (default \"\", truncated to 1000 chars) recorded in the audit event."
  2. First observedv0.1.0

TDQS

A4.9/5.0
Behavior5/5

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

No annotations exist, so the description carries the full burden and does it well: requires confirm=True, refuses rows in converting status, sets status to archived, emits an audit event, and returns the updated item. It also states the record is not deleted, which is the key safety fact for a mutation.

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 tight sentences: the mutation and its non-destructive nature are front-loaded, followed by the sibling routing and the behavioral caveats. No filler.

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, yet the description still notes the updated item is returned. Confirm requirement, status restriction, audit behavior, and reversibility path are all covered, leaving nothing an agent needs to call correctly.

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 confirm and reason are already documented; however, the description adds a genuine constraint on needfix_id (rows in converting status are refused) that the schema does not convey. Confirm semantics are largely repeated from 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 (archive), resource (NeedFix item), and scope (one non-converting item, record retained). It also names what it is not: it does not delete the stored record, and the siblings restore/purge are named for contrast.

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 says when to use it (move an inactive or obsolete row out of the active inbox) and routes to alternatives with conditions: restore for returning to active, purge for permanent deletion.

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