Skip to main content
Glama

Coline

Send message

send_message

Posts a message as the person in a channel, direct message or thread. Use it only when they clearly want it posted.

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>"
    },
    "name": "send_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
textNoThe message, in markdown. Or give content.
typeNoWith conversationId; or give only threadId to reply in that thread.
contentNoThe message as text and mention parts, instead of text.
threadIdNoReply in this message's thread.
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".
sharedFilesNoColine files to share, and what the others may do with them.
conversationIdNoFrom list_conversations.
clientMessageIdNoYour id for this send, so a retry doesn't post it twice.
replyToMessageIdNoQuote this message.
attachmentFileIdsNoUploaded files to attach.

Output Schema

NameRequiredDescriptionDefault
urlYes
messageIdYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds one useful behavioral fact beyond that: the message is posted 'as the person', i.e. under the caller's identity. It omits other relevant traits such as whether the send is undoable and how clientMessageId protects retries.

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 short sentences with the destination scope front-loaded and no filler. It is efficient, though the second sentence is faintly vague in its pronoun reference ('they'), requiring the reader to infer the requesting user.

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

Completeness3/5

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

An output schema exists, so return values need not be explained, and the identity/scope statement covers the core of a send operation. For a ten-parameter mutation tool the description leaves gaps around threading behavior, attachments and retry semantics that the model must recover entirely from the schema.

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 all ten parameters, including enums and the clientMessageId retry note, are documented in the schema itself. The description adds no parameter-level meaning (no explanation of content vs text, threadId-only replies, or attachment limits), 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 gives a specific verb and resource ('Posts a message') plus the destinations it can target ('channel, direct message or thread'), so an agent can distinguish it from send_mail or edit_message without opening the schema. It stops short of explicitly naming a sibling it is not, which keeps it below a 5.

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?

'Use it only when they clearly want it posted' supplies a consent-based gate for when to act, which is real guidance for a write tool. However, it names no alternatives (e.g. send_mail for email, edit_message for changing an existing post) and gives no when-not conditions beyond the intent gate.

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