time-messenger-mcp-server

search_channels

Find channels in a team by name using a search term. Provide the team ID and term to locate relevant channels.

Instructions

Search channels in a team by name

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>",
      "term": "<term>"
    },
    "name": "search_channels"
  }
}

Input Schema

Name	Required	Description	Default
`term`	Yes	Search term
`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?

No annotations are provided, and the description only states the core purpose. It does not disclose behavioral traits like whether the operation is read-only, case sensitivity, pagination, or the response format. The verb 'search' implies no side effects but this is not explicit.

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 one short, front-loaded sentence that conveys all essential information without any redundant words.

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?

The tool is simple and the schema covers parameters fully, but there is no output schema and no behavioral details. The description does not specify the return value or behavior when no matches are found, leaving some ambiguity for a search tool.

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 input schema already provides descriptions for both required parameters (term and team_id) with 100% coverage. The description adds no additional semantic meaning beyond what the schema contains, so a baseline score 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 clearly states the action ('search'), the resource ('channels'), and the scope ('in a team by name'). It distinguishes this from sibling tools like search_messages and search_users by explicitly targeting channels.

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 description implies usage (when you need to find a channel by name within a team) but does not explicitly contrast it with alternatives such as list_channels or get_channel, nor does it state when not to use it.

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