time-messenger-mcp-server

list_channels

Retrieve all channels available to a user within a specific team. Provide the team ID to get a list of channels for that team.

Instructions

List all channels for the user 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_channels"
  }
}

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

A3.5/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states the core function and does not mention whether it is read-only, what 'all channels' includes (e.g., private, archived), pagination, ordering, or any other behavioral traits.

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 that is front-loaded with the verb and resource. Every word earns its place, with no fluff or redundancy.

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?

For a simple one-parameter list tool with no output schema, the description is adequate but not rich. It conveys the purpose clearly but does not describe the return format, scope details, or edge cases, which the agent might need for correct invocation.

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 schema already provides 100% coverage for the single parameter team_id with a description ('Team ID'). The description adds no extra parameter semantics beyond this, so baseline 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') plus resource ('channels') and scope ('for the user in a team'), making it clear what the tool does. It distinguishes itself from sibling tools like get_channel (singular) and search_channels (search-based) by implying a comprehensive list operation.

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 usage context is implied: use this when you need to list all channels for a team. However, no explicit alternatives, exclusions, or when-not-to-use guidance is provided, leaving the agent to infer from sibling tools.

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