Skip to main content
Glama

slack_open_modal

Open a Slack modal to display interactive dialogs or forms within your workspace using the Lightbulb connector.

Instructions

Slack connector operation open_modal (platform tool slack.open_modal).

Routes through /api/tools/invoke under your JWT, tenant, and company scope.

Args: arguments: JSON string of arguments for the connector operation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
argumentsNo{}

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior1/5

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

No annotations provided and description lacks any behavioral details such as required permissions, side effects, or whether the action is destructive or read-only.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short and front-loaded but includes unnecessary routing info and lacks substance.

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?

With no annotations, minimal schema, and a complex action (opening a Slack modal), the description fails to provide essential context for proper usage.

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?

The sole parameter 'arguments' is described as 'JSON string of arguments for the connector operation', but the schema does not define structure, and the description provides no further detail on valid keys or values.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description merely restates the tool name as 'Slack connector operation open_modal' without explaining what opening a modal entails or how it differs from other Slack tools.

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

Usage Guidelines1/5

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

No guidance on when to use this tool versus other Slack tools like slack_views_open or slack_post_message.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/RPasquale/lightbulb-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server