Skip to main content
Glama
shrec

AIWorkhub

by shrec
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

aiworkhub_dashboard_needfix_purge

Destructive

DESTRUCTIVE: permanently delete one archived NeedFix row from the NeedFix table while retaining an audit snapshot.

Instructions

DESTRUCTIVE: permanently delete one archived NeedFix row from the NeedFix table while retaining an audit snapshot.

Use aiworkhub_dashboard_needfix_archive first to archive the item safely, or aiworkhub_dashboard_needfix_restore to recover an archived item instead of deleting it. Requires confirm=True, a non-empty audit_reason, and an already-archived row; records a purged audit event with the row snapshot and permanently deletes the row from the needfix table.

Input Schema

NameRequiredDescriptionDefault
confirmNobool (default False); must be True to permanently purge the NeedFix row.
needfix_idYesstr canonical NeedFix identifier of the archived row to permanently delete.
audit_reasonYesstr non-empty mandatory justification (truncated to 1000 chars) persisted in the purge audit event.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.12.62
    • addedInput schema / properties / audit_reason / description
      Added value: +"str non-empty mandatory justification (truncated to 1000 chars) persisted in the purge audit event."
    • addedInput schema / properties / confirm / description
      Added value: +"bool (default False); must be True to permanently purge the NeedFix row."
    • addedInput schema / properties / needfix_id / description
      Added value: +"str canonical NeedFix identifier of the archived row to permanently delete."
  2. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already carry destructiveHint=true, but the description adds real context beyond them: the confirm=True and non-empty audit_reason gates, the already-archived precondition, and the fact that a purge audit event with a row snapshot is written before permanent deletion. It does not cover what happens to links/tasks attached to the row, which is the main residual risk.

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 'DESTRUCTIVE' and a tight first sentence, then alternatives, then requirements. Slight redundancy: 'permanently delete' is stated twice and the final clause re-explains the already-given row requirement.

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?

Output schema exists and annotations cover the safety profile, so the description needn't explain return values. It covers preconditions and audit side effects well; only the handling of dependent records on purge is unaddressed.

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 confirm, needfix_id and audit_reason are already documented. The description restates confirm=True and 'non-empty audit_reason', which corroborates but adds little new semantics. Baseline 3 applies.

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 ('permanently delete one archived NeedFix row from the NeedFix table') plus a non-obvious side effect (retains an audit snapshot). It is immediately distinguishable from needfix_archive, needfix_restore and the dashboard purge siblings because it names the table and the single-row scope.

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 routes the agent: use needfix_archive first, or needfix_restore to recover an archived item 'instead of deleting it'. The precondition (row must already be archived) further gates correct usage.

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