Skip to main content
Glama

Subscribe channel wake

subscribe_channel_wake

Attach your MCP session notification sink to a channel session ID so the daemon can send channel_wake notifications to it. Requires the channel proxy role.

Instructions

Internal tool reserved for the cross-agent-teams-mcp channel proxy. Attaches the caller's MCP session notification sink to a channel_session_id so the daemon can emit notifications/channel_wake to it. Requires role=channel_proxy.

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_session_id": "<channel_session_id>"
    },
    "name": "subscribe_channel_wake"
  }
}

Input Schema

NameRequiredDescriptionDefault
channel_session_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full load and does disclose the key behavioral facts: it mutates the session's notification binding and requires an elevated role. It omits what happens on repeated calls (does it replace an existing sink or stack?), what error surfaces without the role, and whether the subscription can be detached afterward.

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?

Two compact sentences with the access restriction front-loaded ahead of the effect, so an agent learns it probably should not call this before reading further. No filler, though the role requirement could be more tightly integrated.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter tool with no output schema this covers purpose, permission, and effect adequately. It leaves open the practical questions of obtaining a valid channel_session_id and confirming the subscription succeeded, which matter for a setup operation.

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 0%, so the description must compensate, and it does explain that channel_session_id designates the channel session the notification sink is bound to. It adds no information on where the caller obtains that id, its format, or whether it must match an existing session.

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 gives a specific verb and resource: attaching the caller's MCP session notification sink to a channel_session_id, plus the downstream effect of emitting notifications/channel_wake. The opening line 'internal tool reserved for the cross-agent-teams-mcp channel proxy' also differentiates it from general-purpose siblings like bind_channel, though it does not explicitly contrast the two.

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?

It states the caller population clearly ('reserved for the cross-agent-teams-mcp channel proxy') and the prerequisite ('Requires role=__channel_proxy__'), which functions as an effective when-not-to-use guard. It stops short of naming an alternative or saying what an ordinary agent should do instead of calling this.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.