Skip to main content
Glama

leave

Idempotent

Unsubscribe an agent from #channels; when the last member exits, the channel is removed from the swarm directory.

Instructions

Unsubscribe from #channels. When the last subscribed member leaves a #channel, the channel is removed from the swarm directory.

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": {
      "agent": "<agent>",
      "channels": "<channels>"
    },
    "name": "leave"
  }
}

Input Schema

NameRequiredDescriptionDefault
agentYesYour agent handle (without leading '@'), e.g. 'lead', 'api', or 'db'.
channelsYesChannels to unsubscribe from (each prefixed with '#').

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

The annotations already declare idempotentHint=true and destructiveHint=false, so the description's real contribution is the disclosed side effect: the channel is removed from the swarm directory when the last member leaves. That is non-obvious cascade behavior an agent would otherwise not anticipate, and it is stated plainly. It does not cover failure modes such as leaving a channel you are not a member of.

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?

Two sentences, zero filler. The action comes first and the consequential side effect follows immediately, giving the agent the important caveat up front without padding.

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 two-parameter tool with full schema coverage, annotations, and no output schema, the description covers the action and the one surprising consequence. Only error/edge-case behavior is left unstated, which is a minor gap at this complexity.

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%, with both 'agent' and 'channels' fully documented in the schema including handle format and '#' prefix rules. The description adds no additional parameter meaning, 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?

The description opens with a specific verb and resource: 'Unsubscribe from #channels', which is directly distinguishable from the sibling 'join'. It stops short of naming the inverse operation as the alternative path, but the intent is unambiguous.

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

Usage Guidelines3/5

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

Usage is only implied by the verb 'unsubscribe' and the fact that a 'join' sibling exists. There is no explicit statement of when to call this versus join, or what happens if you attempt to leave a channel you never joined.

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

Deploy Server

Other Tools