Skip to main content
Glama

list_threads

Retrieve this worktree's current thread and repository threads one line each, open and recent first. Call at session start to resume work; set include_closed to review closed threads needing results.

Instructions

This worktree's current thread and the threads of its repository, one line each (open first, most recent activity first): title (the focus's first line), turns, updated_at, and for open threads the declared next's first line with its owner. Closed threads are only counted (closed.count, closed.needs_result) unless include_closed=true. needs_result means the engineer closed it from the screen without a result line; when they ask you to tidy up, call list_threads(include_closed=true), read each thread marked needs_result and fill it with close_thread(case_id, result). For one thread's full state use resume(case_id). Call it (or resume) first in a session, before any other work — always when the host has no session-start hook (e.g. Codex); pass worktree (absolute path) when you are not in the server's cwd. From a chat client (no repository) it also lists open work across all repositories.

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_threads"
  }
}

Input Schema

NameRequiredDescriptionDefault
factsNo
worktreeNo
include_closedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so: it discloses ordering (open first, most recent activity first), that closed threads are only counted unless include_closed=true, the meaning of needs_result, the cwd fallback, and that a chat client with no repository sees open work across all repositories.

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?

Purpose and output shape are front-loaded, and every clause is substantive rather than filler. It is dense and somewhat run-on, packing ordering, closed-thread handling, session-start policy, and cross-repo behavior into one block with little structural separation.

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 a tool with no output schema and no annotations, the description fully characterizes the return lines, ordering, closed-thread counting, and session-entry behavior. The only material omission is the unexplained facts parameter.

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 coverage is 0%, so the description must compensate. It explains include_closed's default behavior and its tidy-up workflow, and defines worktree as an absolute path required when not in the server's cwd. The third parameter, facts, is never mentioned, leaving an optional object parameter undefined.

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 ('list_threads' returns this worktree's current thread and the repository's threads, one line each) plus the exact per-line fields. It also distinguishes itself from siblings by naming resume(case_id) for one thread's full state and close_thread(case_id, result) for filling in results.

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

Usage Guidelines5/5

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

Explicit when-to-use: call it (or resume) first in a session, before any other work, always when the host has no session-start hook such as Codex. It also gives the concrete trigger for include_closed=true ('when they ask you to tidy up') and the condition for passing worktree (not in the server's cwd).

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