Skip to main content
Glama

unpark

Close a parked item as done or dropped, record a resolution note, and archive it so it can be reopened later.

Instructions

Close a parked item once the work is done (done) or abandoned (dropped).

    ``note`` records the resolution (what was done, or why it was dropped). The item is
    archived, not deleted — ``qmx reopen <id>`` brings it back.
    

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": {
      "item_id": "<item_id>"
    },
    "name": "unpark"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNo
statusNodone
item_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does well: it discloses that the item is archived rather than deleted, that the operation is reversible via ``qmx reopen <id>``, and that ``note`` captures the resolution. It omits prerequisites (must the item actually be parked?) and error behavior, but the destructive-vs-archival distinction is exactly the kind of context an agent needs before 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded in the first clause, followed by parameter meaning and then the reversibility guarantee — a sensible ordering. Three short sentences with no padding, though the indentation and doubled backticks are formatting noise.

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 an unannotated mutation with no output schema, the description covers the essential unknowns: terminal states, note semantics, and post-condition (archived, reopenable). What remains missing is preconditions on ``item_id`` and what the call returns, both minor given the tool's simplicity.

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 description coverage is 0%, so the description must compensate and largely does: it explains what ``note`` records and enumerates the meaningful values for ``status`` (``done``/``dropped``), which the schema does not encode as an enum — genuinely valuable. ``item_id`` is left implicit, which is a minor gap for a 3-parameter tool.

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?

The description gives a specific verb+resource combination — closing a parked item — and defines the two terminal outcomes (``done``/``dropped``). It is distinguishable from ``park`` because it explicitly describes the closing/archiving action. It does not name or contrast itself with ``resume_parked``, which sounds semantically adjacent, leaving a small differentiation gap.

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?

It states the triggering condition well: close the item once the work is done or abandoned. That is real when-to-use guidance. However, no alternatives are named (e.g. ``resume_parked`` for putting work back in flight) and no exclusions are given, so the agent must infer the boundary itself.

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