Skip to main content
Glama

list_open_threads

Read-onlyIdempotent

List unfinished threads without changing them, and filter by project or energy to narrow existing work.

Instructions

List unfinished threads without changing them.

    Filter by project or energy when narrowing existing work. Use
    session_digest when you want a session-start summary with reminders and
    resume context instead of the raw thread list. Each thread carries
    advisory return_cue coaching for its resume_step.
    

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum open threads to return (1–500); defaults to 50.
energyNoExact energy filter: low, medium, high or unknown; null includes all energy levels.
project_slugNoRegistered project slug; includes descendants. Null lists open threads across projects.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.22.0
    • addedInput schema / properties / energy / description
      Added value: +"Exact energy filter: low, medium, high or unknown; null includes all energy levels."
    • addedInput schema / properties / limit / description
      Added value: +"Maximum open threads to return (1–500); defaults to 50."
    • addedInput schema / properties / project_slug / description
      Added value: +"Registered project slug; includes descendants. Null lists open threads across projects."
  2. First observedv0.12.0

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so "without changing them" largely restates structured data. The one genuinely additive detail is that each thread's return_cue coaching is advisory rather than enforced, which tells the agent how to interpret output; no ordering, pagination, or auth behavior is described.

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 read-only scope is front-loaded and the sibling comparison follows logically, with no filler sentences. Slight redundancy between "unfinished threads without changing them" and the annotations, and the trailing return_cue note feels appended rather than integrated.

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?

An output schema exists and annotations are rich, so the description needn't document return values or safety. It covers purpose, filtering intent, an alternative route, and the advisory nature of return_cue; only ordering/pagination semantics for the default 50-item limit are left unaddressed.

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%, and the schema itself explains the project_slug descendant expansion, the exact energy enum, and the limit bounds. The description only says filters exist for "project or energy" and omits limit entirely, so it adds little beyond the schema baseline.

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?

The description states a specific verb and resource ("List unfinished threads") plus an invariant scope ("without changing them"), and it explicitly distinguishes the result from session_digest's summary form. An agent can tell this is the raw-list tool versus the digest tool without inspecting either schema.

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?

It says when to apply the filters ("when narrowing existing work") and names an alternative with the exact condition that should redirect the agent: "Use session_digest when you want a session-start summary with reminders and resume context instead of the raw thread list." That is an explicit when-to-use, when-to-use-something-else statement.

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