Skip to main content
Glama

Slack: show home

slack_show_home
Read-only

Select the Home tab in Slack's navigation rail and wait for the sidebar to appear, enabling agents to open Slack's home view.

Instructions

Select the Home tab in Slack's navigation rail and wait for the sidebar to appear. Slack must be running with --force-renderer-accessibility or presses are silently ignored.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "slack_show_home"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations declare a safe read-only, non-destructive, closed-world operation, so the description's extra value is the launch-flag requirement and the silent-failure mode ("presses are silently ignored"), which no annotation conveys. It stops short of describing post-conditions such as how to confirm the Home view actually loaded.

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?

Two sentences, zero waste: the action and its completion signal come first, the environment prerequisite second. Every clause carries actionable information.

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

Completeness5/5

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

For a zero-parameter UI-navigation tool with no output schema, all an agent needs is what the click does, when it is safe, and what failure looks like — all present. Nothing material is missing.

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

Parameters4/5

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

The tool takes zero parameters, so per the baseline this dimension scores 4 by default. There is no parameter meaning the description could add, and it correctly offers none.

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?

States a specific verb and resource ("Select the Home tab in Slack's navigation rail") plus the completion signal ("wait for the sidebar to appear"). It is clearly distinct from the sibling UI-navigation tools (code_show_explorer, slack_filter_channels) without needing the schema.

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?

The description gives the operative precondition for use — Slack must be running with --force-renderer-accessibility — which is exactly the context an agent needs before choosing this tool. It does not, however, contrast the tool with siblings such as slack_filter_channels or say when not to use it.

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