Skip to main content
Glama
RPasquale

lightbulb-mcp

by RPasquale
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

slack_views_push

DestructiveIdempotent

Push a modal view to a Slack workspace through the project-bound connector account. Supply project identifiers and idempotency key to ensure the governed write action is delivered and verified.

Instructions

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

Routes only through the exact project/account governed connector authority.

Args: arguments: JSON string of arguments for the connector operation. project_id: Authenticated Project UUID. project_ref: Exact project correlation reference. connector_account_ref: Project-bound connector account alias. idempotency_key: Stable business-action identity. effect: Claimed read or write effect; Spring verifies it. approval_ref: Approved platform task UUID when resuming a write.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
effectNo
argumentsNo{}
project_idNo
project_refNo
approval_refNo
idempotency_keyNo
connector_account_refNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.1.1
    • addedInput schema / properties / approval_ref
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Approval Ref"
+}
    • addedInput schema / properties / connector_account_ref
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Connector Account Ref"
+}
    • addedInput schema / properties / effect
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Effect"
+}
    • addedInput schema / properties / idempotency_key
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Idempotency Key"
+}
    • addedInput schema / properties / project_id
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Project Id"
+}
    • addedInput schema / properties / project_ref
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Project Ref"
+}
  2. First observedv0.1.0

TDQS

C2.2/5.0
Behavior2/5

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

The annotations already indicate the tool is idempotent, destructive, and not read-only. The description adds no behavioral context beyond these hints—for example, it does not clarify what destructive side effects occur (closing a view?) or what idempotency means in this context. The phrase 'Routes only through the exact project/account governed connector authority' is about routing, not behavior.

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?

The description is compact, with a clear title line, a routing sentence, and a bullet-like list of parameters. It avoids unnecessary filler and stays within a reasonable length. The only minor redundancy is repeating 'project/account governed connector authority' twice in nearly identical form, but overall the structure is efficient.

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?

The description lacks essential context about how this tool fits into the Slack ecosystem. It does not mention the underlying Slack API endpoint, what a 'view' is, or what the expected output looks like (despite an output schema supposedly existing). It also does not explain the relationship between the 'arguments' JSON and the dedicated parameters, nor when the approval_ref is required, leaving an agent without enough information to invoke it correctly.

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?

The schema has zero description coverage, so the one-liners compensate somewhat. Each parameter gets a terse semantic label (e.g., 'Authenticated Project UUID', 'Stable business-action identity'), which adds meaning beyond the raw string type. However, the 'arguments' parameter is only described as 'JSON string of arguments for the connector operation' without specifying the expected structure, leaving the most important parameter ambiguous.

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 states it is a 'Slack connector operation views_push' but does not explain what 'views_push' actually does, such as pushing a modal to a Slack user or updating a view. It also does not distinguish it from sibling tools like slack_views_open, slack_views_publish, or slack_views_update, which have overlapping names. The routing note is an implementation detail rather than a functional purpose.

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?

There is no guidance on when to use this tool compared to the many other Slack view tools (open, publish, update) or when to provide arguments versus using the dedicated parameters. The description does not mention prerequisites, such as having an existing view token or a specific permission scope, nor does it indicate whether the tool is intended for interactive components or standalone use.

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

Deploy Server

Other Tools