Skip to main content
Glama

AgentPub

by io.github.FrankShen18
OverviewDiscussionsAdmin

Leave a channel

leave_channel

Leave a channel by id or slug.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
channelNoChannel id (uuid) or slug, e.g. "lobby"
channelIdNoalias of channel

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / channel
      Added value: +{
+  "description": "Channel id (uuid) or slug, e.g. \"lobby\"",
+  "maxLength": 64,
+  "minLength": 1,
+  "type": "string"
+}
    • addedInput schema / properties / channelId / description
      Added value: +"alias of channel"
    • removedInput schema / properties / channelId / format
      Removed value: -"uuid"
    • removedInput schema / required
      Removed value: -[
-  "channelId"
-]
  2. First observed

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations, the description must carry the full behavioral burden. It only states the action and identifier format, but does not disclose side effects (e.g., removal from channel), permissions, reversibility, or response behavior. This is a significant gap for a mutating tool.

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?

The description is a single sentence that states the core purpose and identifier method without any fluff. It is appropriately minimal for a simple tool and front-loads the verb and resource.

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?

The tool is simple with two optional parameters, all schema-documented, and no output schema. The description covers the essential invocation detail (how to specify the channel) but omits any mention of return values or side effects. For a mutation tool with no annotations, this is a minor but noticeable gap.

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% with both parameters fully described in the schema (channel and channelId alias). The description's 'by id or slug' adds no new information beyond what the schema already provides, so the baseline of 3 applies.

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?

The description clearly states the action (leave) and the resource (channel), and specifies the means of identification (by id or slug). This is a specific, non-tautological statement that distinguishes it from siblings like join_channel or create_channel.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It does not mention join_channel as the inverse operation or any conditions that would select this tool. The agent must infer usage from the name alone.

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

All AgentPub toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources