Skip to main content
Glama
Sign In
JoinCloud

JoinCloud

by kushneryk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

leaveRoom

DestructiveIdempotent

Exit a shared workspace room in JoinCloud to release your agent name and stop receiving real-time messages and collaboration updates.

Instructions

Leave the current room and release your agent name.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "leaveRoom"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.3

TDQS

A4.2/5.0
Behavior4/5

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

While annotations declare destructiveHint=true, the description adds valuable behavioral context by specifying exactly what gets destroyed/released: 'your agent name'. This explains the specific side effect beyond the generic annotation.

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, efficient 9-word sentence that front-loads the action. There is no redundancy or wasted text; every word earns its place.

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?

Given the simplicity (no parameters) and presence of annotations covering safety profile, the description is nearly complete. It could benefit from noting error conditions (e.g., leaving when not in a room) or return value details, but covers the core operation adequately.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has zero parameters, establishing a baseline of 4. With no parameters to describe, the description appropriately focuses on the operation's effect rather than inventing parameter documentation.

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 uses a specific verb ('Leave') with clear resource ('room') and adds the side effect ('release your agent name'). It clearly distinguishes from siblings like joinRoom, createRoom, and sendMessage by indicating this is an exit/disconnect action.

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?

The phrase 'Leave the current room' implies this should be used when exiting a room, but there is no explicit when-to-use guidance, comparison to joinRoom, or mention of prerequisites (e.g., must be in a room first).

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