Skip to main content
Glama

list_parked

Lists parked items by repository or global scope, status, or semantic query so users can review open, done, dropped, closed, or stale entries and decide what to keep or drop.

Instructions

List parked items — only call when the user asks ("what did I park?", "parked items").

    Scoped to ``cwd``'s repo (or ``scope``) plus global items; with neither, every scope.
    ``status``: ``open`` (default) | ``done`` | ``dropped`` | ``closed`` | ``all``. ``query``
    ranks by meaning. ``stale_only`` keeps items untouched long enough to need a keep-or-drop
    review (each item also carries a ``stale`` flag).
    

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_parked"
  }
}

Input Schema

NameRequiredDescriptionDefault
kNo
cwdNo
queryNo
scopeNo
statusNoopen
all_scopesNo
stale_onlyNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.0

TDQS

A3.9/5.0
Behavior4/5

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

No annotations exist, so the description carries the full burden, and it does disclose non-obvious behavior: scoping precedence (cwd repo + global, or every scope when neither is set), the default status of open, semantic ranking via query, and the per-item stale flag. It omits pagination/limit behavior and never states the read-only nature explicitly, leaving gaps for a no-annotation tool.

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 gating condition before any parameter detail, and each sentence adds information. The inline backtick formatting and run-on multi-clause sentence slightly hurt scannability but there is no filler.

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?

Seven parameters at 0% schema coverage and no annotations set a high bar; the output schema relieves the need to explain return values, and the description covers most filtering semantics. However, k (an unexplained integer defaulting to 20) and all_scopes are left entirely opaque, so an agent cannot confidently control result size or scope expansion.

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?

With 0% schema description coverage, the description must compensate, and it documents five of seven parameters substantively: cwd/scope precedence, the full status enum including modes not visible in the schema, query as semantic ranking, and stale_only's review semantics. k and all_scopes are left undefined, which is a real residual gap.

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?

Opens with a specific verb and resource ("List parked items") and immediately narrows its scope with an example of the user phrasing that should trigger it. An agent can tell it apart from park/resume_parked/unpark, though it never names any sibling explicitly.

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?

Explicit trigger condition ("only call when the user asks", with quoted example questions) plus the scoping rule for cwd/scope/global precedence. It stops short of naming alternatives — an agent must infer when to prefer query or get instead.

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