Skip to main content
Glama

channels_connect_session_options

Read-onlyIdempotent

Which channels a connect session can connect right now, and the methods of each: {channels: {whatsapp: [qr, pairing_code], telegram: [qr, phone], viber: [qr]}}. A channel that is not listed is refused by channels.connect_session.start with unsupported_channel. Read this instead of hard-coding the list: channels and methods are added over time.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "channels_connect_session_options"
  }
}

Input Schema

NameRequiredDescriptionDefault
in_workspaceNoRun this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds useful context beyond that: the set is dynamic over time, and a channel missing from the output will cause a downstream unsupported_channel refusal. That is real behavioral context that the annotations do not provide.

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?

It is two tightly written sentences with the return shape front-loaded as an inline example, followed by the downstream consequence and the anti-hard-coding instruction. There is no filler, and every sentence adds distinct information.

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?

Although there is no output schema, the description inlines the exact response shape including per-channel method lists, which covers the return-value gap. Combined with the dynamic-set caveat, the downstream error code, and a fully described parameter, an agent has everything it needs to call and interpret this 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?

There is a single optional parameter, and schema description coverage is 100%, so the schema already explains in_workspace fully, including that nothing is stored and other sessions are unaffected. The description adds nothing about the parameter, which is acceptable at full coverage, so this stays at the baseline of 3.

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?

The description uses a specific verb-and-resource framing: it returns which channels a connect session can connect right now and the methods for each. It also names a concrete consumer, channels.connect_session.start, and its unsupported_channel refusal, which sets it apart from a plain channel listing. It could be slightly sharper about how it differs from generic siblings like channels_list.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"Read this instead of hard-coding the list" is an explicit instruction to call this tool rather than guess. The description also gives context about the consequence of using the data, since unlisted channels are refused by channels.connect_session.start. What's missing is an explicit statement about when not to call it, though the read-only preview role is strongly implied.

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.