Skip to main content
Glama
Sign In
AIWorkhub

AIWorkhub

by shrec
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

needfix_restore

Idempotent

Restore an archived NeedFix to the inbox or a selected status, bringing it back into the active workflow for continued handling.

Instructions

Explicitly restore an archived NeedFix.

Use this to bring an archived NeedFix back into the inbox; use needfix_archive to retire an active one.

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>"
    },
    "name": "needfix_restore"
  }
}

Input Schema

NameRequiredDescriptionDefault
needfix_idYesId of an archived NeedFix, e.g. NF-2026-01447; a NeedFix in any other status is refused.
target_statusNoStatus to restore into: captured, triaged, accepted or deferred; default captured.captured

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.12.67
    • addedInput schema / properties / needfix_id / description
      Added value: +"Id of an archived NeedFix, e.g. NF-2026-01447; a NeedFix in any other status is refused."
    • addedInput schema / properties / target_status / description
      Added value: +"Status to restore into: captured, triaged, accepted or deferred; default captured."
  2. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare the mutation profile (readOnlyHint=false, idempotentHint=true, destructiveHint=false), so the bar is lower. The description adds that the effect is a return to the inbox, but says nothing beyond the schema about what happens to linked tasks or subtasks on restore, which is the main residual risk for a state-changing operation.

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?

Two short sentences, action and precondition front-loaded, with the alternative held to a single clause. No redundant restatement of the tool name or filler.

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 a two-parameter state-transition tool with full annotations, a complete schema, and no output schema, the description covers what the agent needs to select and call it. The only small gap is that the 'archived-only, otherwise refused' guard lives solely in the schema rather than the description.

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%, and the schema itself documents the ID format example and the four valid target_status values plus the default. The description adds no parameter-level meaning of its own, so the 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 ('restore') on a specific resource ('an archived NeedFix') along with the source state precondition. Naming needfix_archive as the counter-operation lets an agent distinguish the pair without opening either 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?

Gives a clear positive trigger ('bring an archived NeedFix back into the inbox') and points to the inverse tool (needfix_archive) for retiring an active one. It does not address other restore-adjacent siblings like needfix_convert or needfix_reopen_superseded_task_link, so the routing guidance is clear but not exhaustive.

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