Skip to main content
Glama

open_dm

Idempotent

Opens a 1:1 direct message channel with another account—or returns the existing channel—so you can send and read messages using the returned channelId. Provide the peer's UUID or unique display name.

Instructions

Opens a 1:1 direct message channel with another account (or returns the existing one). Use the returned channelId with send/read. peer is the other account's UUID or (when unique) display name.

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": {
      "peer": "<peer>"
    },
    "name": "open_dm"
  }
}

Input Schema

NameRequiredDescriptionDefault
peerYesOther account's UUID or unique display name

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.0.1
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observedv2.1.1

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare a non-read-only, idempotent, non-destructive operation; the description adds real context beyond them by explaining that an existing channel is returned rather than duplicated, and that the result yields a channelId consumed by send/read. It also implies a failure mode when a display name is not unique, though it does not say what error or result that produces.

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 sentences, front-loaded with the action and its get-or-create semantics, followed by the practical next step and the peer argument note. No redundant or ceremonial wording; every clause carries information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter tool with annotations covering the safety profile and no output schema, the description supplies what is needed: what it creates, that it is idempotent, the key returned (channelId), and how to use it next. Nothing essential to correct invocation is missing.

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 schema already types and documents 'peer'; the description adds meaning by restating the two accepted forms (UUID preferred, display name only 'when unique'), flagging the ambiguity constraint the agent must respect. The gain over the schema is real but modest, since the schema field text already mentions 'unique display name'.

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 names a specific verb and resource ('Opens a 1:1 direct message channel with another account') and pins the scope to a peer-to-peer DM, which implicitly separates it from create_channel-style tools that create named/group channels. The parenthetical '(or returns the existing one)' further distinguishes its idempotent get-or-create behavior from a plain creation tool, so an agent can select it without opening the schema.

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?

It gives a clear downstream workflow: 'Use the returned channelId with send/read,' which tells the agent this is the prerequisite step before messaging. It does not state explicit exclusions or point at alternatives such as list_dms or list_accounts for resolving an unknown peer, so it stops short of full when/when-not guidance.

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