Skip to main content
Glama
PhononX

Carbon Voice

by PhononX
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

create_direct_message

Send a direct message to one or more users by user ID or email, including a text transcript or link. Use to contact people outside an existing conversation thread.

Instructions

Send a direct message to one or more people, by user ID or email. USE WHEN: Reaching people outside an existing conversation. Address it with to.user_ids or to.emails. Requires transcript or links. USE INSTEAD: create_conversation_message when a conversation already exists — a DM starts a separate thread rather than joining it. FIRST: to.user_ids comes from search_users (field id) — call it first if you don't have one. EXAMPLE: {"to":{"user_ids":["user-abc"]},"transcript":"Quick question about the deck."} RETURNS: {message: {id, link, transcript?, status, conversation_id, created_at, ...}}. ERROR BAD_REQUEST: A user ID is invalid, or neither transcript nor links was provided. — Resolve people with search_users — never pass a display name as a user ID — and include a transcript or links.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toYesRecipients: `user_ids` (from `search_users`) and/or `emails`. At least one required.
linksNoArray of links to be attached to the message
transcriptNoThe Message transcript will be used to generate audio using text-to-speech
workspace_idNoThe workspace ID to send the message topersonal
from_message_idNoMessage ID to be used as a base for the new message. (Optional only when from_message_type is NewMessage)
from_message_typeNoFrom Message typeNewMessage

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.10.0
    • addedInput schema / properties / to / description
      Added value: +"Recipients: `user_ids` (from `search_users`) and/or `emails`. At least one required."
  2. Changed1 schema field changedv2.8.17
    • changedInput schema / properties / from_message_type / enum
      Previous value: -[
-  "PreRecorded",
-  "NewMessage",
-  "Forward"
-]New value: +[
+  "PreRecorded",
+  "NewMessage",
+  "Forward",
+  "MessageId"
+]
  3. First observed

TDQS

A4.9/5.0
Behavior5/5

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

The description goes beyond the minimal annotations (readOnlyHint=false, destructiveHint=false) by disclosing the requirement for transcript or links, the error condition (BAD_REQUEST for invalid user ID or missing transcript/links), and the fact that a DM starts a separate thread. It also mentions the return shape and example, offering substantial behavioral context without contradicting annotations.

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 structured with clear sections (USE WHEN, USE INSTEAD, FIRST, EXAMPLE, RETURNS, ERROR) that are all informative and directly relevant. Every sentence adds value, and it is front-loaded with the core action. No fluff or redundancy.

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?

Given the tool's complexity (6 parameters, nested object, enum, and no output schema), the description covers all essential aspects: usage context, prerequisites, example, return format, and error handling. An agent can confidently call this tool correctly based on the description alone.

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 meaning beyond the schema by clarifying that 'to.user_ids' comes from search_users and warning against passing display names as user IDs. It also highlights the transcript/links requirement, which is not immediately obvious from the schema alone.

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 states a specific verb and resource: 'Send a direct message to one or more people, by user ID or email.' It clearly distinguishes from the sibling tool by noting that a DM starts a separate thread rather than joining an existing conversation, making it unmistakable which tool to use.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly states when to use this tool ('Reaching people outside an existing conversation') and when to use an alternative ('USE INSTEAD: create_conversation_message when a conversation already exists'). It also provides a prerequisite step (calling search_users to obtain user_ids), which is valuable guidance for the agent.

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