Skip to main content
Glama
inboxd
by 47star

get_slack_thread

Read a Slack thread's archived root and replies in order to retrieve the full conversation from a local archive.

Instructions

Read one Slack thread's locally archived root and replies in chronological order.

conversation_id comes from list_slack_conversations or a message. thread_id is the root's Slack timestamp: use a message's thread_id, or source_id for a root without thread_id. A reply's source_id is not its root timestamp. Returns bounded previews and sender names, with deleted items marked. Open read_request for full text. Continue with next_request. reported_reply_count is the last collected Slack value, not a guarantee of complete history.

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": {
      "conversation_id": "<conversation_id>",
      "thread_id": "<thread_id>"
    },
    "name": "get_slack_thread"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
cursorNo
thread_idYes
conversation_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and does so well: it discloses bounded previews, that deleted items are marked, that content is locally archived rather than live, and that reported_reply_count may understate history. It omits error behavior for a missing or inaccessible thread and any mention of permissions, which keeps it from a 5.

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?

Sized appropriately for a tool with non-obvious identifier semantics, front-loaded with the purpose before the ID rules. The telegraphic sentence fragments are efficient but occasionally read as notes rather than guidance.

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 4-parameter, 0%-schema-coverage, no-annotation, no-output-schema tool, the description covers the hard parts (ID provenance, pagination, preview limits, count caveat). It still leaves two of four parameters undocumented, which is a meaningful gap an agent must guess around.

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 0%, so the description must compensate, and it explains thread_id and conversation_id in useful detail, including the subtle point that a reply's source_id is not its root timestamp. However, limit and cursor are never explained; 'bounded previews' and 'next_request' only loosely imply them, and the default of 50 and max of 100 go unmentioned.

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 opens with a precise verb and resource: 'Read one Slack thread's locally archived root and replies in chronological order.' The scope (a single thread, root plus replies, chronological) and the 'locally archived' qualifier distinguish it clearly from siblings like search_messages, get_message, and get_conversation without naming them.

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

Usage Guidelines4/5

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

It tells the agent where IDs originate ('conversation_id comes from list_slack_conversations or a message') and routes follow-up work to read_request for full text and next_request for continuation. It does not explicitly say when to prefer a sibling like get_conversation or search_messages instead, so it stops short of full alternative routing.

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