Skip to main content
Glama

channels_connect_session_submit

Hand a connect session what the person typed: exactly ONE of phone, code, password.

  • need_phone → phone (international format). WhatsApp answers need_pairing_code with the 8-character pairing_code to type on the phone; Telegram sends a code and answers need_code.

  • need_code → code (Telegram). Answers connected, or need_password when the account has two-step verification.

  • need_password → password (Telegram two-step verification).

A mistyped code or password is refused with error_type validation and the session stays where it is: submit again. 10 submits per session, then rate_limited and the session ends. Nothing submitted here is logged or stored after the session ends.

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": {
      "session_id": "<session_id>"
    },
    "name": "channels_connect_session_submit"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeNoThe sign-in code Telegram sent. Only at need_code.
phoneNoThe phone number, e.g. +380501234567. Only at need_phone.
passwordNoThe Telegram two-step verification password. Only at need_password.
session_idYesThe session_id that channels.connect_session.start returned.
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.9/5.0
Behavior5/5

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

Annotations already flag openWorldHint and non-idempotency, and the description adds substantial context beyond them: validation errors leave the session in place, a 10-submit cap triggers rate_limited and ends the session, and nothing is logged or stored. This is rich behavioral disclosure.

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?

Front-loaded with the core rule, then a tight bulleted state map, then error/rate-limit behavior. Every sentence carries information; no filler.

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?

No output schema exists, yet the description explains the possible answers (connected, need_code, need_password, need_pairing_code, validation, rate_limited), so an agent can interpret results. Complete for a stateful multi-step tool.

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 100%, so the baseline is 3, but the description adds real meaning: the mutual-exclusivity constraint ('exactly ONE'), international phone format, the 8-character pairing_code flow, and which session state each parameter belongs to. It stops short of explaining in_workspace, which the schema covers.

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

Purpose5/5

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

States a specific verb and resource ('Hand a connect session what the person typed') and immediately constrains it to exactly one of phone/code/password. This clearly separates it from siblings like channels_connect_session_start, _get, and _cancel.

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

Usage Guidelines5/5

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

Gives an explicit state-to-parameter mapping (need_phone → phone, need_code → code, need_password → password) with the expected follow-up states for each. An agent knows exactly when to call this and what to pass.

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.