Skip to main content
Glama

Slack_connect

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Slack Send Message

slack_send_message
Idempotent

Send a message to a Slack channel. Bot auto-joins the channel if needed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYesMessage text (supports Slack markdown)
channelYesChannel ID to send the message to
thread_tsNoThread timestamp to reply in a thread (optional)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okNoWhether the message was sent successfully
tsNoTimestamp of sent message
errorNoError code if message send failed
channelNoChannel ID where message was sent
messageNoMessage object containing details

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "channel": {
+      "description": "Channel ID where message was sent",
+      "type": "string"
+    },
+    "error": {
+      "description": "Error code if message send failed",
+      "type": "string"
+    },
+    "message": {
+      "description": "Message object containing details",
+      "properties": {
+        "text": {
+          "description": "Message text",
+          "type": "string"
+        },
+        "ts": {
+          "description": "Message timestamp",
+          "type": "string"
+        },
+        "type": {
+          "description": "Message type",
+          "type": "string"
+        },
+        "user": {
+          "description": "User ID of sender",
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "ok": {
+      "description": "Whether the message was sent successfully",
+      "type": "boolean"
+    },
+    "ts": {
+      "description": "Timestamp of sent message",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "channel": "C01234ABCDE",
+    "text": "Hello team, here's an update on the project."
+  },
+  {
+    "channel": "C01234ABCDE",
+    "text": "Great point! I agree.",
+    "thread_ts": "1609459200.123456"
+  }
+]
  3. First observed

TDQS

A4/5.0
Behavior4/5

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

The description adds behavioral context beyond annotations: 'Bot auto-joins the channel if needed.' This discloses a side effect (joining a channel) that is not evident from the annotations alone.

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 two concise sentences with no wasted words. It is front-loaded with the core purpose followed by a key behavioral detail.

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 simple tool with full schema coverage and an output schema, the description adequately covers the main action and a notable side effect. It could mention error scenarios or permission requirements, but given the context, it is solid.

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?

The tool description itself does not elaborate on parameters, but the input schema has 100% coverage with clear descriptions (e.g., text supports Slack markdown). According to the rule, baseline 3 is appropriate.

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 clearly states the specific action: sending a message to a Slack channel. It distinguishes from sibling tools like slack_join_channel (joining a channel) and slack_channel_history (reading history) by its verb and resource.

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?

The description implicitly suggests usage by mentioning auto-join, indicating that prior channel joining is unnecessary. However, it does not explicitly state when to use this tool over alternatives or provide exclusion criteria.

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

All Slack_connect toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources