Skip to main content
Glama

Attach a channel

attach_channel
Idempotent

Attach an existing organization channel to an agent, so the channel's events wake it. Find the channel with list_channels. A webhook channel lets callers outside Valet reach the agent. Attaching a channel that is already attached reports it and changes nothing. Slack needs a Slack app and a browser, so for Slack this gives the step to take and attaches nothing. An app takes no organization channels: create its own with create_channel. Returns the agent and channel, with attached true and already when the agent held it. 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": {
      "name": "<name>",
      "channel": "<channel>"
    },
    "name": "attach_channel"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesThe agent's name, as list_services shows it: the agent to attach the channel to.
channelYesThe organization channel's name, from list_channels.
org_nameNoThe Valet organization both belong to. Omit to use the organization the account joined first.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / anyOf
      Previous value: -[
      -  {
      -    "additionalProperties": false,
      -    "properties": {
      -      "agent": {
      -        "description": "Name of the agent the call acted on.",
      -        "type": "string"
      -      },
      -      "already": {
      -        "description": "True when the channel was already in this state before the call, so nothing changed. Absent when this call changed it.",
      -        "type": "boolean"
      -      },
      -      "attached": {
      -        "description": "True when the channel is attached to the agent after the call, false when it is not. attach_channel always reports true; detach_channel always reports false.",
      -        "type": "boolean"
      -      },
      -      "channel": {
      -        "description": "Name the channel is attached under, which is the name detach_channel takes.",
      -        "type": "string"
      -      },
      -      "org": {
      -        "description": "Name of the Valet organization the call acted in.",
      -        "type": "string"
      -      }
      -    },
      -    "required": [
      -      "org",
      -      "agent",
      -      "channel",
      -      "attached"
      -    ],
      -    "type": "object"
      -  },
      -  {
      -    "additionalProperties": false,
      -    "properties": {
      -      "org": {
      -        "description": "Name of the Valet organization the call acted in.",
      -        "type": "string"
      -      },
      -      "step": {
      -        "description": "What the person does in a browser, such as authorizing a service. Nothing has changed until they do it.",
      -        "type": "string"
      -      },
      -      "url": {
      -        "description": "Address of the page where the person finishes the step. Absent when the page has no address to give.",
      -        "type": "string"
      -      }
      -    },
      -    "required": [
      -      "org",
      -      "step"
      -    ],
      -    "type": "object"
      -  }
      -]New value: +[
      +  {
      +    "additionalProperties": false,
      +    "properties": {
      +      "agent": {
      +        "description": "Name of the agent the call acted on.",
      +        "type": "string"
      +      },
      +      "already": {
      +        "description": "True when the agent already held the channel, so nothing changed. Absent when this call attached it.",
      +        "type": "boolean"
      +      },
      +      "attached": {
      +        "description": "Always true: the agent holds the channel after the call.",
      +        "type": "boolean"
      +      },
      +      "channel": {
      +        "description": "Name the channel is attached under, which is the name detach_channel takes.",
      +        "type": "string"
      +      },
      +      "org": {
      +        "description": "Name of the Valet organization the call acted in.",
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "org",
      +      "agent",
      +      "channel",
      +      "attached"
      +    ],
      +    "type": "object"
      +  },
      +  {
      +    "additionalProperties": false,
      +    "properties": {
      +      "org": {
      +        "description": "Name of the Valet organization the call acted in.",
      +        "type": "string"
      +      },
      +      "step": {
      +        "description": "What the person does in a browser to finish attaching the channel, such as authorizing Slack. Returned instead of an attach result; nothing has changed until they do it.",
      +        "type": "string"
      +      },
      +      "url": {
      +        "description": "Address of the page where the person finishes the step. Absent when the page has no address to give.",
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "org",
      +      "step"
      +    ],
      +    "type": "object"
      +  }
      +]
  2. Changed1 schema field changed
    • changedInput schema / properties / name / description
      Previous value: -"The agent's name."New value: +"The agent's name, as list_services shows it: the agent to attach the channel to."
  3. Changed3 schema fields changed
    • changedInput schema / properties / channel / description
      Previous value: -"Required. The organization channel's name, from list_channels."New value: +"The organization channel's name, from list_channels."
    • changedInput schema / properties / name / description
      Previous value: -"Required. The agent's name."New value: +"The agent's name."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "anyOf": [
      +    {
      +      "additionalProperties": false,
      +      "properties": {
      +        "agent": {
      +          "description": "Name of the agent the call acted on.",
      +          "type": "string"
      +        },
      +        "already": {
      +          "description": "True when the channel was already in this state before the call, so nothing changed. Absent when this call changed it.",
      +          "type": "boolean"
      +        },
      +        "attached": {
      +          "description": "True when the channel is attached to the agent after the call, false when it is not. attach_channel always reports true; detach_channel always reports false.",
      +          "type": "boolean"
      +        },
      +        "channel": {
      +          "description": "Name the channel is attached under, which is the name detach_channel takes.",
      +          "type": "string"
      +        },
      +        "org": {
      +          "description": "Name of the Valet organization the call acted in.",
      +          "type": "string"
      +        }
      +      },
      +      "required": [
      +        "org",
      +        "agent",
      +        "channel",
      +        "attached"
      +      ],
      +      "type": "object"
      +    },
      +    {
      +      "additionalProperties": false,
      +      "properties": {
      +        "org": {
      +          "description": "Name of the Valet organization the call acted in.",
      +          "type": "string"
      +        },
      +        "step": {
      +          "description": "What the person does in a browser, such as authorizing a service. Nothing has changed until they do it.",
      +          "type": "string"
      +        },
      +        "url": {
      +          "description": "Address of the page where the person finishes the step. Absent when the page has no address to give.",
      +          "type": "string"
      +        }
      +      },
      +      "required": [
      +        "org",
      +        "step"
      +      ],
      +      "type": "object"
      +    }
      +  ],
      +  "type": "object"
      +}
  4. Added

TDQS

A4.3/5.0
Behavior4/5

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

Goes well beyond the annotations: it discloses the auth prerequisite ("Requires connecting a Valet account"), the idempotent no-op behavior with its return shape ("attached true and already"), and the Slack special case that attaches nothing. The only soft spot is that it does not say precisely what the Slack path returns.

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 core action and is dense with useful content, but the Slack sentence is telegraphic ("this gives the step to take") and slows parsing. No sentence is wasted, though several are compressed to the point of awkwardness.

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?

For a three-parameter mutation with an output schema, it covers nearly everything: auth requirement, idempotency, Slack exception, and failure/neutral outcomes. What is missing is only the exact response shape in the Slack case, a minor gap given an output schema exists.

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 coverage is 100%, so name, channel, and org_name are already fully documented including the org_name default. The description adds only the provenance hint that the channel value comes from list_channels, which is marginal beyond the schema.

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 ("Attach an existing organization channel to an agent") plus the mechanism ("so the channel's events wake it"). It is immediately distinguishable from create_channel and list_channels, which are also referenced.

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 explicit routing: use list_channels to find the channel, use create_channel instead when the target is an app, and notes Slack requires a different path entirely. It also states what happens on a redundant call, so the agent knows the no-op case in advance.

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