time-messenger-mcp-server

reorder_channel_categories

Set the sidebar order of channel categories by providing every category ID for a team exactly once in the desired sequence.

Instructions

Set the sidebar order of channel categories. category_ids must list every category of the team exactly once.

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>",
      "category_ids": "<category_ids>"
    },
    "name": "reorder_channel_categories"
  }
}

Input Schema

Name	Required	Description	Default
`team_id`	Yes	Team ID.
`category_ids`	Yes	All category IDs of the team in the desired order.

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.4.0Nov 4, 2026

TDQS

B3.4/5.0

Behavior3/5

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

With no annotations, the description carries the behavior burden alone. It usefully discloses full-replacement semantics ("every category of the team exactly once"), which tells the agent this is not a partial reorder. It omits failure modes: what happens if an ID is missing, duplicated, or unknown, and whether the call requires elevated permissions.

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?

Two sentences, zero filler, with the action stated first and the critical constraint immediately after. Nothing could be removed without losing information.

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 wholesale-reorder mutation with no annotations and no output schema, the definition covers intent and the completeness constraint but says nothing about permissions, error behavior on invalid IDs, or whether the operation is atomic. Adequate to attempt a call, incomplete for handling edge cases.

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?

Schema coverage is already 100%, so baseline is 3, but the description adds a real constraint beyond the schema text: each category ID must appear exactly once, meaning no duplicates and no omissions. That extra rule materially changes how the agent must construct the array.

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?

"Set the sidebar order of channel categories" gives a specific verb (set order) and resource (channel categories), which distinguishes it from update_channel_category or move_channel_to_category. It doesn't explicitly name those siblings, but the ordering focus is unambiguous.

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 statement of when to use this vs. update_channel_category or move_channel_to_category, nor any prerequisite context (e.g., whether admin rights are needed, or that a list must be read first via list_channel_categories). The second sentence is a data constraint, not usage guidance.

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