Generate a permanent Slack message link by providing the channel ID and message timestamp. Share stable references to any message.
Get a permanent link to a Slack message.
| Name | Required | Description | Default |
|---|---|---|---|
| channel | Yes | Channel ID containing the message | |
| message_ts | Yes | Timestamp of the message |
Changes observed during successful MCP inspections.
v0.1.8Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden of behavioral disclosure. It communicates the output is a permanent link and implicitly suggests a read-only operation, but it does not mention permissions, error behavior, or the exact return format beyond 'link'.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, front-loadedsentence with no wasted words. It states the core purpose immediately and requires no additional elaboration.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a low-complexity tool with full schema coverage, the description is mostly adequate. However, with no annotations and no output schema, it could usefully specify that the return value is a URL string or mention any prerequisites for finding the message.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema already covers both parameters with descriptions, so schema_description_coverage is 100%. The description adds no parameter-specific semantics beyond the context that the link applies to a Slack message.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action ('Get') and the specific result ('a permanent link to a Slack message'). This is distinct from all sibling tools, none of which involve generating permalinks.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies the tool should be used when a permanent link to a Slack message is needed, but it does not explicitly mention when to prefer this over alternatives or provide exclusions. There is no obvious sibling alternative, so the lack of guidance is a mild gap.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.