Skip to main content
Glama

resume_parked

Restore the original context behind a parked item by retrieving it with the past chat turns that best match, so you can continue work with more than a one-line note.

Instructions

Pick a parked item back up: the item plus the past chat turns that best match it, so the original context is restored, not just the one-line note.

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": "resume_parked"
  }
}

Input Schema

NameRequiredDescriptionDefault
kNo
item_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations supplied, the description must carry the behavioral burden, and it does add real value: it discloses that the response includes the item plus contextually matched chat turns, which tells the agent what it gets rather than just what it triggers. However, it is silent on whether resuming mutates state (does the item leave the parked list?), whether it fails if the item is already active, and whether the retrieval is a side-effect-free read. Those gaps matter for a tool whose name implies a state transition.

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?

A single sentence, front-loaded with the action and followed by the payoff, with no boilerplate or repetition. The em-dash aside ("not just the one-line note") is a slightly rhetorical flourish, but it does carry information about the difference from simply viewing the note.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter tool with no output schema and no annotations, the description covers the outcome reasonably well but leaves two things an agent needs: what "k" does and whether resuming changes parked state. It is adequate to attempt a call, not adequate to predict the call's effect.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description needed to explain both parameters and does not. "item_id" is only obliquely implied by "the item," and the "k" parameter (default 3) is never mentioned at all — the phrase "the past chat turns that best match it" hints that a count or relevance limit exists but never says what it controls or that it is tunable.

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 concrete verb+resource ("pick a parked item back up") and goes further by stating what comes back: the item plus matching past chat turns. That is more than a restatement of the name. It stops short of distinguishing itself from adjacent operations like unpark, so it lands at 4 rather than 5.

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?

The phrase "pick a parked item back up" implies the situation (you have something parked and want it back in play), and the closing clause implies why you would choose this over just reading the note. There is no explicit when-not guidance, no statement of preconditions (must the item still be parked?), and no routing to an alternative.

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