time-messenger-mcp-server

list_threads

Retrieve all threads you follow in a team to see your active conversations at a glance.

Instructions

List all threads that the user is following in a team

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "team_id": "<team_id>"
    },
    "name": "list_threads"
  }
}

Input Schema

Name	Required	Description	Default
`team_id`	Yes	Team ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.3.0Aug 1, 2026

TDQS

B3.2/5.0

Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It reveals the filtering behavior (only threads the user is following), but omits other important traits such as whether the operation is read-only, what data is returned (e.g., thread metadata vs. messages), and any authentication requirements.

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?

The description is a single, concise sentence with no filler. It is front-loaded and easy to parse.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite being a simple tool, the lack of output schema and annotations means the description should provide more completeness about return values or behavior. It doesn't mention what the list results contain (e.g., thread objects, IDs) or any pagination, making it incomplete for an agent to fully understand consequences.

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?

The single parameter team_id has 100% schema coverage with its description 'Team ID'. The tool description adds no additional meaning beyond the schema, so the baseline of 3 is appropriate.

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 uses a specific verb ('List') and resource ('threads') with clear scope: threads the user is following in a team. This differentiates it from sibling tools like get_thread (single thread) and get_thread_messages (messages within a thread).

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?

The description gives no explicit guidance on when to use this tool versus alternatives like get_thread or get_thread_messages. The use case is implied (listing followed threads) but no when-not-to-use or alternative references are provided.

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