Skip to main content
Glama

Coline

Add tab to conversation

add_conversation_tab

Pins a file or folder as a tab above a channel or direct message, for everyone 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>",
      "type": "<type>",
      "conversationId": "<conversationId>",
      "tab": "<tab>"
    },
    "name": "add_conversation_tab"
  }
}

Input Schema

NameRequiredDescriptionDefault
tabYes
typeYes
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".
conversationIdYesChannel or direct message id, from list_conversations.

Output Schema

NameRequiredDescriptionDefault
tabsYes
activeTabIdYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=false, so the mutation profile is known. The description adds one genuinely useful behavioral fact beyond that: the tab is visible "for everyone in it", i.e. the effect is conversation-wide rather than personal. It says nothing about required permissions, what happens on duplicate tabs (relevant given idempotentHint=false), or failure modes.

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?

A single front-loaded sentence with no filler; the verb and target lead. It is efficient, though the brevity comes partly at the cost of the accuracy gaps noted above.

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?

An output schema exists, so return values need not be described, and annotations cover the safety profile. What remains missing for a 4-parameter mutation is coverage of the unmentioned repository tab variant, the channel/dm/task type distinction, and duplicate/permission behavior.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 50%: workspace and conversationId already carry descriptive text in the schema, while the 'type' enum (channel/dm/task) and the 'tab' oneOf payload are undocumented there. The description partially gestures at the tab payload ("file or folder") but omits the repository variant, the optional title field, and any meaning for the conversation type enum, so it does not compensate for the coverage gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a concrete verb and resource ("pins a file or folder as a tab") and names the placement scope ("above a channel or direct message"), which is clearer than the title alone. However, it under-describes the tool relative to its own schema: the tab payload also supports "repository" targets and the conversation type allows "task", neither of which the sentence mentions, so an agent could wrongly conclude repository tabs are unsupported.

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 never states when to use this tool versus alternatives such as open_conversation_tab or remove_conversation_tab, nor does it note prerequisites like membership in the conversation. At best usage is implied by the verb "pins"; there are no explicit inclusion or exclusion conditions.

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