Skip to main content
Glama

list_threads

Retrieve saved web chat conversations in newest-first order so agents can inspect, reference, or resume prior threads.

Instructions

Saved conversations, newest first.

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

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose the sort order (newest first), which is genuine behavioral information, but it says nothing about whether results are truncated, paginated, scoped to a user, or read-only. For a zero-annotation tool this leaves significant gaps.

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 four-word sentence with no filler, and the ordering detail is front-loaded rather than buried. It is efficient, though the terseness is part of why other dimensions fall short rather than a strength in itself.

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?

An output schema exists, so return values need not be explained, and with zero parameters the schema burden is minimal. Still, the absence of annotations means the description should say more about scope, limits, and read-only behavior to be fully sufficient. It is minimally adequate for a simple list tool.

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?

The tool takes no parameters and the schema confirms an empty properties object, so there is nothing for the description to disambiguate. Baseline 4 applies for a zero-parameter tool; the description neither helps nor hurts here.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The phrase "Saved conversations, newest first" identifies the resource (saved conversations) and the ordering, so an agent can infer it lists threads. However, it is a noun phrase with no verb, and it never distinguishes itself from the sibling thread_history, which plausibly also returns conversations. The purpose is inferable but not stated as an explicit action.

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

Usage Guidelines2/5

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

There is no guidance on when to call this instead of thread_history or why one would choose this listing over the history tool. The only implicit signal is the newest-first ordering, which an agent must interpret on its own. No exclusions, prerequisites, or alternatives are mentioned.

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