Skip to main content
Glama
Sign In

OrgGen AI

by ai.orggen
OverviewDiscussionsAdmin

archive_task

Destructive

Archives a task (or several — taskId accepts an array, up to 100): it leaves the lists and the card indicators, without being destroyed. It is the action that replaces a deletion. Archiving never cascades to subtasks: if it keeps LIVE ones, the response SAYS so via liveChildren + liveChildrenNote (the action still succeeds; subtasks are archived explicitly if that is intended). In BATCH form, each id is archived INDEPENDENTLY — an id not found never prevents the others from succeeding — and the response carries succeeded/failed instead of the flat fields of the single action.

Input Schema

NameRequiredDescriptionDefault
taskIdYesONE identifier, or UP TO 100 (array) — each one is archived INDEPENDENTLY: a refusal (locked block, task not found) on one does not prevent the others from succeeding. In batch form, the response carries `succeeded`/`failed` instead of the flat fields of the single action.
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) — chacun s’archive INDÉPENDAMMENT : un refus (bloc verrouillé, tâche introuvable) sur l’un n’empêche JAMAIS les autres d’aboutir. Sous forme lot, la réponse porte `succeeded`/`failed` au lieu des champs plats du geste unitaire."New value: +"ONE identifier, or UP TO 100 (array) — each one is archived INDEPENDENTLY: a refusal (locked block, task not found) on one does not prevent the others from succeeding. In batch form, the response carries `succeeded`/`failed` instead of the flat fields of the single action."
  3. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Annotations only say destructiveHint=true; the description carries the real behavioral load: the task leaves lists and card indicators but is not destroyed, archiving never cascades and the response reports `liveChildren`/`liveChildrenNote`, and batch calls return `succeeded`/`failed` while still succeeding partially. These are non-obvious traits an agent cannot infer from annotations or schema.

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 core action and its key property (non-destructive, replaces deletion), then layers edge cases in descending importance. Slightly redundant, since its batch-independence sentence largely repeats the `taskId` schema description verbatim in meaning.

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?

No output schema exists, and the description compensates by describing the response shape in both modes (`liveChildren`/`liveChildrenNote` for single, `succeeded`/`failed` for batch). Combined with the mutation-safety picture, an agent has enough to call and interpret it correctly.

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 documents `taskId` array bounds, `claimToken` secret/lease semantics, and `expectedProjectId` targeting. The description only restates the array form and batch independence, adding little beyond the already-rich schema; baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific verb (archives) and resource (a task), and clarifies scope by noting `taskId` may be an array of up to 100. It also frames the tool as the non-destructive replacement for deletion, which positions it well. It never names the sibling it inverts (`unarchive_task`) or contrasts with `update_task`, so sibling disambiguation is incomplete.

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 clear conditions: use this instead of deletion; archive subtasks explicitly rather than expecting a cascade; in batch form ids are processed independently. It stops short of stating when NOT to use it or naming `unarchive_task` as the reversal path, which is the obvious alternative an agent would need.

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