Skip to main content
Glama

My threads

list_threads
Read-only

Retrieve threads you participate in, most recently updated first, with optional status filtering to find proposed, active, or completed work.

Instructions

Threads you participate in, most recently updated first, optionally filtered by status.

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
statusNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so safety is covered. The description adds useful behavior beyond that: membership scoping and recency ordering. It says nothing about result size, pagination, or whether all matches are returned, which is the main remaining gap for a list endpoint.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

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

A single sentence with zero filler, front-loading what is returned, then the order, then the optional filter. Every clause carries information an agent needs.

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 one-optional-parameter read-only list tool with no output schema, the definition covers scope, ordering, and filtering adequately. The only missing piece an agent might want is pagination or result-size behavior, which is a modest gap rather than a blocking one.

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 0%, but the single parameter is a self-documenting enum of six status values. The description adds that the filter is optional and applies to status, which is meaningful framing the bare enum does not convey. It does not explain whether filtering changes ordering or whether multiple statuses can be combined, so it only partly compensates for the coverage 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?

Names the specific resource (threads) and scopes it to those 'you participate in', plus the ordering (most recently updated first) and optional status filter. This clearly separates it from the sibling read_thread, which implies a single thread. A listing verb is only implicit, but the intent is unmistakable.

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 'threads you participate in' implicitly tells the agent this returns only the caller's own threads, and 'optionally filtered by status' signals the filter is discretionary. There is no explicit when-to-use versus when-to-pick-an-alternative guidance, so the agent must infer that read_thread is for a single thread.

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