Skip to main content
Glama

send_message

Send messages to Slack channels or reply in threads to communicate with team members directly from AI assistants.

Instructions

Send a message to a channel

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
channelYesChannel ID
textYesMessage text
thread_tsNoOptional thread timestamp to reply to

Implementation Reference

  • The main handler function for the 'send_message' tool. It validates input using sendMessageSchema, calls Slack's chat.postMessage API, and returns the result.
    export async function sendMessage(client: SlackClientWrapper, args: unknown) {
      const params = sendMessageSchema.parse(args);
    
      return await client.safeCall(async () => {
        const result = await client.getClient().chat.postMessage({
          channel: params.channel,
          text: params.text,
          thread_ts: params.thread_ts,
        });
    
        return {
          ok: true,
          channel: result.channel,
          ts: result.ts,
          message: result.message,
        };
      });
    }
  • Zod schema used for input validation in the send_message handler.
    export const sendMessageSchema = z.object({
      channel: channelIdSchema,
      text: z.string().min(1),
      thread_ts: timestampSchema.optional(),
    });
  • src/index.ts:173-194 (registration)
    Tool definition for 'send_message' in the tools array returned by list_tools, including input schema.
    {
      name: 'send_message',
      description: 'Send a message to a channel',
      inputSchema: {
        type: 'object',
        properties: {
          channel: {
            type: 'string',
            description: 'Channel ID',
          },
          text: {
            type: 'string',
            description: 'Message text',
          },
          thread_ts: {
            type: 'string',
            description: 'Optional thread timestamp to reply to',
          },
        },
        required: ['channel', 'text'],
      },
    },
  • src/index.ts:426-426 (registration)
    Handler registration mapping 'send_message' calls to messageTools.sendMessage in the toolHandlers object for call_tool requests.
    send_message: (args) => messageTools.sendMessage(slackClient, args),
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. While 'send' implies a write operation, it doesn't disclose permission requirements, rate limits, error conditions, or what happens to the message after sending. For a mutation tool with zero annotation coverage, this leaves significant behavioral gaps.

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 a single, efficient sentence with zero wasted words. It's appropriately sized for a simple tool and gets straight to the point without unnecessary elaboration.

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?

For a basic messaging tool with good schema coverage but no annotations or output schema, the description provides the minimum viable information about what the tool does. However, it lacks important context about behavioral traits and differentiation from sibling tools, leaving gaps in overall completeness.

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%, so the input schema already documents all three parameters thoroughly. The description adds no additional parameter information beyond what's in the schema. This meets the baseline expectation when schema coverage is complete.

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 clearly states the action ('send') and target ('message to a channel'), providing a specific verb+resource combination. However, it doesn't distinguish this tool from its sibling 'send_formatted_message', which appears to serve a similar purpose with different formatting capabilities.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives like 'send_formatted_message' or 'update_message'. There's no mention of prerequisites, appropriate contexts, or exclusions that would help an agent choose between similar messaging tools.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Hais/slack-bot-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server