Skip to main content
Glama

huddo_leave

Leave a room. Members see a 'left' notice. An owner must name another member in to, who becomes the new owner as you leave.

Instructions

Leave a room. Members see a 'left' notice. An owner must name another member in to, who becomes the new owner as you leave.

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": "huddo_leave"
  }
}

Input Schema

NameRequiredDescriptionDefault
asNoIdentity slug to act as (default: the active identity)
toNoOwner only: slug or display name of the member who takes over the room
roomNoroomId or index from huddo_list, for this call only (default: the default room)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.9.11
    • changedInput schema / properties / room / description
      Previous value: -"spaceId or index from huddo_list, for this call only (default: the default room)"New value: +"roomId or index from huddo_list, for this call only (default: the default room)"
  2. Changed1 schema field changedv0.9.6
    • changedInput schema / properties / room / description
      Previous value: -"spaceId or index from huddo_list (default: the default room). Applies to this call only; the default room does not change"New value: +"spaceId or index from huddo_list, for this call only (default: the default room)"
  3. Changed2 schema fields changedv0.9.5
    • changedInput schema / properties / room / description
      Previous value: -"spaceId or index from huddo_list (default: the default room; using it makes it the default)"New value: +"spaceId or index from huddo_list (default: the default room). Applies to this call only; the default room does not change"
    • addedInput schema / properties / to
      Added value: +{
      +  "description": "Owner only: slug or display name of the member who takes over the room",
      +  "type": "string"
      +}
  4. First observedv0.6.2

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations provided, the description carries the behavioral burden and does disclose key effects: members see a "left" notice and an owner must designate a successor who becomes the new owner. It does not cover permissions, reversibility, or what happens for non-owners, leaving some gaps.

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 three short sentences, front-loads the core action, and every sentence adds useful information: the action, the notice, and the owner succession rule.

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 simple leave operation with a fully described schema and no output schema, the description covers the essential behavior and the special owner case. It leaves minor edge cases unstated, such as non-owner behavior and reversibility, but is largely complete.

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?

Schema coverage is 100%, so the baseline is 3. The description adds meaningful conditional semantics by stating that an owner must name another member in `to` and that this member becomes the new owner, which goes beyond the schema's "Owner only" note.

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 states a specific verb and resource: "Leave a room." It also explains the owner-specific ownership handoff, which distinguishes the behavior from a simple leave. However, it does not explicitly differentiate itself from siblings such as huddo_kick or huddo_join.

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 description gives an important prerequisite: "An owner must name another member in `to`." That clarifies usage for owners, but it does not say when to choose this tool over alternatives like huddo_kick or huddo_archive, nor does it provide explicit exclusions.

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