Skip to main content
Glama

Coline

Open a direct message

open_direct_message
Idempotent

Opens the person's direct message with one or more teammates (agents can join a group chat), starting it if there isn't one yet. With two or more others it's a group chat, which can have a 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": {
      "workspace": "<workspace>",
      "memberUserIds": "<memberUserIds>"
    },
    "name": "open_direct_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoGroup chats only.
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".
memberUserIdsYesThe others in it, from find_people.

Output Schema

NameRequiredDescriptionDefault
dmIdYes
createdYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=false, idempotentHint=true and destructiveHint=false; the description usefully explains what 'opens' means (creates the DM if absent) and adds group-chat naming behavior. It stops short of describing permission requirements, what happens to an existing DM's state, or visibility rules, so it adds only moderate context beyond structured fields.

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?

Two sentences, front-loaded with the core action and followed by the group-chat nuance; no wasted wording. Slight redundancy between 'one or more teammates' and 'two or more others' but it is functional.

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 three-parameter tool with full schema coverage, an output schema, and annotations, the description covers purpose, creation-if-absent semantics, and the group-chat naming condition. Missing only secondary details like permission prerequisites or behavior when a DM already exists.

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, but the description adds a genuinely new conditional relationship: 'with two or more others it's a group chat, which can have a name', linking the `name` parameter's applicability to the size of memberUserIds. The schema only says 'Group chats only.' without that threshold.

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?

States a specific verb and resource ('Opens the person's direct message') and clarifies scope with 'one or more teammates' plus the group-chat case. It does not explicitly contrast with siblings such as send_message or leave_direct_message, so it falls short of full sibling differentiation.

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 context is implied by 'starting it if there isn't one yet', which tells the agent the tool is safe to call when a conversation may not exist. However, there is no explicit statement of when to prefer this over send_message or other siblings, and no exclusions.

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