Skip to main content
Glama

Coline

Open conversation tab

open_conversation_tab
Read-onlyIdempotent

What a tab above a conversation shows: its file, or its folder and what's 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>",
      "tabId": "<tabId>"
    },
    "name": "open_conversation_tab"
  }
}

Input Schema

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

Output Schema

NameRequiredDescriptionDefault
kindYes
tabIdYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

C2.3/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered; the description adds nothing beyond that. It says nothing about side effects of opening a tab, whether the tab must already exist, or what happens for an unknown tabId — context that matters for a tool with four required parameters.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single short sentence with no padding, so there is no verbosity problem. The issue is that the sentence is not front-loaded with an action and spends its only clause on content rather than on what the call does.

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

Completeness4/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 explained, and annotations carry the safety profile. Still, for a four-required-parameter tool the description omits the core contract (that it opens/navigates to a tab) and leaves the enum `type` and `tabId` meaning entirely to inference.

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 coverage is only 50%: workspace and conversationId are described in the schema, but `type` (the enum channel/dm/task) and `tabId` are undocumented anywhere. The description does not mention any parameter, so it fails to compensate for the gap as low-coverage schemas require.

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

Purpose2/5

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

The description never says the tool opens a tab; it describes tab content ("What a tab above a conversation shows: its file, or its folder and what's in it"), which reads like a noun definition rather than an action. It gestures at the resource (conversation tabs) but supplies no verb and does not distinguish itself from siblings such as show_conversation or add_conversation_tab.

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 when-to-use, when-not-to-use, or alternative-routing guidance at all. An agent gets no signal on why it would open a tab versus reading or showing the conversation, and the content-oriented phrasing arguably points toward a display/read sibling instead.

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