Skip to main content
Glama
macula-io

Macula MCP

by macula-io
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

mesh_leave_room

Leave a mesh room: publishes participant_left (or room_closed) and stops watching the topic. Transcript stays readable.

Instructions

Leave a room: publishes participant_left (or room_closed with close: 1, which only means something from the agent that opened it -- nothing enforces it) and stops watching the topic. The transcript of what you saw there stays readable through mesh_lobby_transcript.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
closeNo1 to publish room_closed instead of participant_left.
room_topicYesA room you are in (see mesh_rooms).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.37.0
    • removedInput schema / properties / host
      Removed value: -{
-  "description": "Station to connect through, \"host[:port]\". Defaults to station-de-frankfurt.macula.io:4433.",
-  "type": "string"
-}
  2. First observedv0.28.7

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the published events, the subscription teardown, and explicitly warns that the `close` flag is advisory ("nothing enforces it"). It omits error behavior (e.g., leaving a room you are not in) and any return shape.

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?

Front-loaded with the core action and its effects, and every clause conveys distinct information. The parenthetical about `close` is slightly dense but earns its place by flagging a non-enforced behavior.

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, no-output-schema tool with no annotations, the description covers side effects, the close-flag caveat, and where the transcript remains readable. Remaining gaps (error cases, confirmation of room membership) are minor.

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 baseline is 3, but the description adds real meaning for `close: 1` by explaining the semantic trigger condition (must be the opening agent) and that enforcement does not exist. That is genuine value beyond the schema's bare "1 to publish room_closed".

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?

Starts with a specific verb+resource ("Leave a room") and immediately names the observable side effects (publishes participant_left, stops watching the topic). It is clearly distinguishable from siblings like mesh_join_room, mesh_open_room, and mesh_unobserve_lobby.

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?

States the key selection condition for the `close` flag ("only means something from the agent that opened it") and routes the agent to mesh_lobby_transcript for viewing the retained transcript. It doesn't spell out when to prefer this over other disengagement tools, but the usage context is clear.

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