Skip to main content
Glama
Sign In
nomos-slack-mcp

nomos-slack-mcp

by project-nomos
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

slack_reply_thread

Reply directly in a Slack thread as the authenticated user, using channel, thread timestamp, and markdown text to post the response.

Instructions

Reply in a Slack thread AS YOU. The reply appears as if you typed it in the thread.

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": {
      "channel": "<channel>",
      "thread_ts": "<thread_ts>",
      "text": "<text>"
    },
    "name": "slack_reply_thread"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesThe reply text. Supports Slack markdown.
channelYesChannel containing the thread (#name, @user, or ID).
thread_tsYesTimestamp of the thread's parent message.
workspaceNoWorkspace alias. Omit to use default.
also_send_to_channelNoAlso post the reply to the channel (default false).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.5

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations provided, the description carries the behavioral transparency burden. It does disclose a meaningful behavioral trait: the reply is posted as the user, not as a generic bot. It does not cover permissions, reversibility, or whether the reply is publicly visible, but the identity effect is a useful and non-obvious disclosure.

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 extremely concise, with two short sentences that each add value: one states the action and target, and the other clarifies the identity and visible outcome. There is no filler or redundancy.

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 reply action with a fully documented schema and no output schema, the description is largely complete. It gives the core action and identity effect, and the schema covers parameters like workspace and also_send_to_channel. It only lacks explicit usage boundaries or permission notes, which would be helpful but are not essential for this simple tool.

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 input schema already provides descriptions for all five parameters, so the schema carries the parameter semantics burden. The description adds no extra parameter-level detail, which matches the baseline of 3 for high schema coverage.

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 uses a specific verb and resource: 'Reply in a Slack thread.' It clearly distinguishes this tool from siblings like slack_send_message by focusing on thread context, and adds the important nuance that the reply appears 'AS YOU,' which directly defines the tool's identity behavior.

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 makes the primary usage context clear: replying in a Slack thread. However, it does not explicitly mention when not to use it or how it differs from alternative tools like slack_send_message or slack_react, leaving some routing decisions to 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