Skip to main content
Glama

slack_api

Call Slack Web API methods through Slack CLI with HTTP fallback to send messages, fetch conversation history, or verify authentication.

Instructions

Call a Slack Web API method via Slack CLI (slack api family.method key=value) with HTTP API fallback. Example method: chat.postMessage, conversations.history, auth.test.

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": {
      "method": "<method>"
    },
    "name": "slack_api"
  }
}

Input Schema

NameRequiredDescriptionDefault
textNo
fieldsNoExtra key=value fields passed to slack api
methodYesSlack Web API method, e.g. chat.postMessage
channelNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It usefully discloses the dual execution path (Slack CLI with HTTP API fallback), which is real behavioral information, but omits whether authentication/workspace tokens are required, what errors look like, and — critically — that the effect (read vs. destructive write) is entirely determined by the chosen `method`.

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 compact sentences, front-loaded with the invocation pattern, with the examples appended rather than buried. Slight redundancy between 'family.method' and 'Example method', but nothing that wastes the agent's attention.

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

Completeness2/5

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

This is a high-complexity generic proxy (any Slack method, arbitrary extra fields), with no annotations and no output schema, so the description must do more. It never explains what the top-level `text` and `channel` parameters are for, whether the tool returns raw Slack JSON, or how failures surface — all things an agent needs before calling an untyped passthrough that can mutate data.

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 coverage is 50%: `method` and `fields` are documented in the schema. The description adds real meaning by showing the `family.method` convention and the `key=value` shape of `fields`, but the top-level `text` and `channel` properties are unexplained in both the schema and the description, so their relation to `fields`/the method remains ambiguous.

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 a concrete verb and resource ('Call a Slack Web API method') and gives the exact CLI invocation form (`slack api family.method key=value`) plus three example methods. That is enough for an agent to know it is a generic Slack passthrough, though it never explicitly contrasts itself with the generic `call_api` / `call_cli` siblings.

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?

There is no statement of when to prefer this over `call_api`, `call_cli`, or `route`, nor any exclusions or prerequisites. The only contextual cue is 'with HTTP API fallback', which describes mechanism rather than selection criteria, leaving the agent to infer which Slack-related tool to pick.

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