Skip to main content
Glama

Reauthorize a channel

reauthorize_channel
Read-onlyIdempotent

Renew the third-party authorization of an organization's Slack or Telegram channel, for a channel whose workspace access was revoked or whose bot scopes changed. The step happens in a browser or a terminal, so the answer carries a step that names the valet channels reauthorize command, and the url of the Integrations page when it has one. It changes nothing itself. A channel with no credentials (cron, heartbeat, webhook, email, mcp) is refused. Requires connecting a Valet account.

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": {
      "channel": "<channel>"
    },
    "name": "reauthorize_channel"
  }
}

Input Schema

NameRequiredDescriptionDefault
channelYesThe channel's name in the organization.
org_nameNoThe Valet organization the channel belongs to. Omit to use the organization the account joined first.

Output Schema

NameRequiredDescriptionDefault
orgYesName of the Valet organization the call acted in.
urlNoAddress of the page where the person finishes the step. Absent when the page has no address to give.
stepYesWhat the person does to renew the channel's authorization, such as reauthorizing Slack or reconnecting Telegram. Always returned: this tool changes nothing itself.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / properties / step / description
      Previous value: -"What the person does in a browser, such as authorizing a service. Nothing has changed until they do it."New value: +"What the person does to renew the channel's authorization, such as reauthorizing Slack or reconnecting Telegram. Always returned: this tool changes nothing itself."
  2. Changed4 schema fields changed
    • changedInput schema / properties / channel / description
      Previous value: -"Required. The channel's name in the organization."New value: +"The channel's name in the organization."
    • addedOutput schema / properties / org / description
      Added value: +"Name of the Valet organization the call acted in."
    • addedOutput schema / properties / step / description
      Added value: +"What the person does in a browser, such as authorizing a service. Nothing has changed until they do it."
    • addedOutput schema / properties / url / description
      Added value: +"Address of the page where the person finishes the step. Absent when the page has no address to give."
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": false,
      +  "properties": {
      +    "org": {
      +      "type": "string"
      +    },
      +    "step": {
      +      "type": "string"
      +    },
      +    "url": {
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "org",
      +    "step"
      +  ],
      +  "type": "object"
      +}
  4. Added

TDQS

A3.9/5.0
Behavior4/5

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

Goes well beyond the annotations by disclosing that the real work happens in a browser or terminal, that the response carries a step naming the `valet channels reauthorize` command plus an Integrations page URL, and that the call itself changes nothing. The auth requirement and refusal cases add real operational context that readOnlyHint/idempotentHint cannot convey.

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?

Front-loads the purpose, then conditions, then the refusal case and prerequisite; each sentence carries information. A few phrases are slightly indirect ('The step happens in a browser or a terminal') but nothing is filler.

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?

Covers what the tool does, when it applies, what it refuses, and the prerequisite account requirement; the output shape is backed by an output schema, so the brief mention of the returned step and URL is sufficient. The only gap is that the reader must infer how this differs from the connector equivalent.

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 description coverage is 100%, so both `channel` and `org_name` are already documented. The description mentions the organization's channel but adds no syntax, format, or default behavior beyond what the schema states, so the baseline of 3 applies.

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?

States a specific verb and resource ('Renew the third-party authorization of ... Slack or Telegram channel') and scopes it to revoked-access or changed-scope cases. It separates itself from the connector sibling implicitly by naming channel types rather than explicitly, so an agent must rely on the name alone to distinguish it from reauthorize_connector.

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?

Gives clear triggering conditions (workspace access revoked, bot scopes changed) and an explicit exclusion (channels with no credentials: cron, heartbeat, webhook, email, mcp are refused), plus a prerequisite (a connected Valet account). It does not name a sibling alternative for connector-based authorization, but the guidance is otherwise unambiguous.

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