Skip to main content
Glama
Sign In

OrgGen AI

by ai.orggen
OverviewDiscussionsAdmin

unarchive_task

Destructive

Puts a task (or several — taskId accepts an array) back into live work. Same batch contract as archive_task: succeeded/failed, each id independent.

Input Schema

NameRequiredDescriptionDefault
taskIdYesONE identifier, or UP TO 100 (array) — same contract as `archive_task`: each id is unarchived INDEPENDENTLY, `succeeded`/`failed` in batch form.
claimTokenNoThe token of YOUR claim (returned by `claim_task`) — REQUIRED to write to a task a lease holds: without it, the refusal is `CLAIM_HELD`; a stale token gives `CLAIM_LOST`. A SECRET that stays out of every written text. Any write that carries it extends the lease without touching the declared progress; the end of the task (`done`, archiving, back to `todo`) releases the claim. On a task nobody holds, the field stays empty.
expectedProjectIdNoUUID of the project targeted by THIS call. ACTUALLY targets this project instead of the session project. Refused without changing anything if access is not granted.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / claimToken
      Added value: +{
+  "description": "The token of YOUR claim (returned by `claim_task`) — REQUIRED to write to a task a lease holds: without it, the refusal is `CLAIM_HELD`; a stale token gives `CLAIM_LOST`. A SECRET that stays out of every written text. Any write that carries it extends the lease without touching the declared progress; the end of the task (`done`, archiving, back to `todo`) releases the claim. On a task nobody holds, the field stays empty.",
+  "maxLength": 200,
+  "minLength": 8,
+  "type": "string"
+}
  2. Changed2 schema fields changed
    • changedInput schema / properties / expectedProjectId / description
      Previous value: -"UUID du projet visé par CET appel. Cible RÉELLEMENT ce projet au lieu du projet de session. Refusé sans rien modifier si l'accès n'est pas accordé."New value: +"UUID of the project targeted by THIS call. ACTUALLY targets this project instead of the session project. Refused without changing anything if access is not granted."
    • changedInput schema / properties / taskId / description
      Previous value: -"UN identifiant, ou JUSQU’À 100 (tableau) — même contrat que `archive_task` : chaque id se désarchive INDÉPENDAMMENT, `succeeded`/`failed` sous forme lot."New value: +"ONE identifier, or UP TO 100 (array) — same contract as `archive_task`: each id is unarchived INDEPENDENTLY, `succeeded`/`failed` in batch form."
  3. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations declare destructiveHint=true and readOnlyHint=false, and the description adds real value on top: the batch contract, per-id independence, and the `succeeded`/`failed` result shape — behavior an agent needs before firing 100 ids. It doesn't discuss claim/lease interaction, but the claimToken schema description already handles that thoroughly.

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 compact sentences with the core action and the batch independence rule front-loaded. Nothing redundant and nothing wasted.

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?

No output schema exists, but the description supplies the result contract (`succeeded`/`failed`, per-id outcomes) and the claim/lease requirements are fully spelled out in the schema. Only the absence of explicit alternatives keeps it short of perfect.

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%, so the schema already carries parameter meaning; baseline 3 applies. The description's note that `taskId` accepts an array is a restatement of the schema's anyOf rather than new semantic detail.

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 action ("Puts a task ... back into live work") and immediately covers the multi-id case. It also names the sibling it mirrors (`archive_task`), so an agent can place it precisely in the lifecycle without reading further.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

Usage is implied by the name and phrasing (restore an archived task into active work), and referencing `archive_task`'s contract helps the agent pick the right batch semantics. But there is no explicit when-to-use/when-not guidance versus alternatives such as `update_task` for status changes or `move_task_to_project`.

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

All OrgGen AI toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources