Skip to main content
Glama

Coline

Leave direct message

leave_direct_message
DestructiveIdempotent

Takes the person out of a direct message or group chat. When nobody's left, it's deleted.

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": {
      "workspace": "<workspace>",
      "dmId": "<dmId>"
    },
    "name": "leave_direct_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
dmIdYesDirect message id from list_conversations.
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".

Output Schema

NameRequiredDescriptionDefault
okYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered. The description adds genuinely new behavior the annotations don't express: the cascade consequence that a conversation with no remaining participants is deleted, which matters to an agent deciding whether to leave a two-person DM. It doesn't mention permission requirements or whether history is retained for other members.

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 short sentences, zero filler, with the action front-loaded and the side effect immediately after. Every sentence 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?

With 2 well-documented required parameters, full annotations, and an output schema, the description only needs to convey the action and its consequence, which it does. The one gap is that it doesn't state the effect on the other participants' view of the conversation or whether the caller can rejoin.

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%, and both parameters already carry descriptions plus cross-references (dmId 'from list_conversations', workspace slug 'from workspaces.list'). The description adds nothing about either parameter, so the baseline 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 uses a clear verb phrase ('Takes the person out of a direct message or group chat') and names the resource (DM / group chat). It's specific enough to act on, but it never compares itself to the sibling 'leave_channel', so the DM-vs-channel boundary is only implied by the word 'direct message'.

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 implied by the resource scope: this is for DMs and group chats, and 'leave_channel' is the obvious alternative for channels, but the description never says so. There is no explicit when-to-use/when-not-to-use statement and no guidance for the single-caller case where the conversation would be deleted instead.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources