Skip to main content
Glama

Coline

Add a channel to a team

add_team_channel

Links a channel to a team; a default channel is joined by everyone who joins the team. A private channel can only be linked by someone in it.

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": {
      "workspace": "<workspace>",
      "teamId": "<teamId>",
      "channelId": "<channelId>"
    },
    "name": "add_team_channel"
  }
}

Input Schema

NameRequiredDescriptionDefault
teamIdYesTeam id from list_teams.
channelIdYes
isDefaultNo
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".

Output Schema

NameRequiredDescriptionDefault
teamChannelYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, non-idempotent, non-destructive mutation. The description adds two useful behavioral facts beyond that: linking as default causes all future team joiners to be added, and private channels require membership to link. It does not say what happens if the channel is already linked, which matters given idempotentHint=false.

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?

Two short sentences, front-loaded with the core action, with no filler. Slightly terse in that the permission precondition is packed into a closing clause rather than flagged as a requirement.

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

Completeness5/5

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

With annotations covering safety profile and an output schema covering return values, the description only needs to convey the semantic side effect and the access constraint for linking private channels, and it does both in two sentences.

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?

Schema coverage is 50%, with channelId and isDefault undocumented. The description implicitly explains what a default channel means (so it indirectly grounds isDefault), but it never explains the channelId parameter or the isDefault flag explicitly, so the gap is only partly compensated. Baseline 3 for partial schema coverage.

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?

"Links a channel to a team" states a specific verb and resource, making it clearly distinct from sibling mutations such as add_team_member or remove_team_channel. It is clear but does not explicitly contrast itself with any named alternative.

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 gives a real precondition ("a private channel can only be linked by someone in it") and explains the meaning of linking as default, but never states when to choose this tool over alternatives like add_team_drive or which cases require a different call.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources