Skip to main content
Glama
Sign In
UnClick MCP Server

UnClick MCP Server

by malamutemayhem
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

slack_action

Send, read, search, or react to Slack messages, reply in threads, list channels, and upload files via a single action-based call.

Instructions

Perform a Slack action: slack_send, slack_read, slack_search, slack_thread_reply, slack_channels, slack_react, slack_upload.

Input Schema

NameRequiredDescriptionDefault
textNo
emojiNo
limitNo
queryNo
actionYes
channelNo
bot_tokenNoSlack bot token (xoxb-...). Optional when Slack is connected in UnClick or SLACK_BOT_TOKEN is set.
thread_tsNo
timestampNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.1.11
    • addedInput schema / properties / bot_token / description
      Added value: +"Slack bot token (xoxb-...). Optional when Slack is connected in UnClick or SLACK_BOT_TOKEN is set."
    • changedInput schema / required
      Previous value: -[
-  "action",
-  "bot_token"
-]New value: +[
+  "action"
+]
  2. Addedv0.1.5

TDQS

C2.6/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It does not disclose which actions are reads versus writes, auth requirements, side effects, rate limits, or return behavior; the action names only weakly imply mutation.

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?

The description is a single front-loaded sentence with no wasted prose. It is concise, though the dense list format sacrifices some readability for a complex dispatcher.

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

Completeness1/5

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

For a nine-parameter, no-annotation dispatcher with no output schema, the description is not complete. It omits per-action required parameters, authentication behavior, side effects, and expected results.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 11% (one of nine parameters documented), and the description adds only the allowed action values. It does not explain how text, channel, thread_ts, timestamp, emoji, query, limit, or bot_token map to specific actions.

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 names the resource (Slack) and enumerates seven concrete operations, so an agent can identify it as a multiplexed Slack action tool. However, the verb 'Perform' is vague and the action labels are not described in terms of outcomes.

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?

It lists action names but gives no criteria for choosing between slack_send, slack_read, slack_search, slack_thread_reply, slack_channels, slack_react, and slack_upload. There is no when-not-to-use guidance or comparison to alternatives.

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