Skip to main content
Glama
MCP Dokploy Online
by igoruam

notification-testSlackConnection

Idempotent

Tests a Slack webhook connection by sending a notification to the specified channel, verifying the integration is configured correctly before use.

Instructions

POST /notification.testSlackConnection

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": {
      "webhookUrl": "<webhookUrl>",
      "channel": "<channel>"
    },
    "name": "notification-testSlackConnection"
  }
}

Input Schema

NameRequiredDescriptionDefault
channelYes
webhookUrlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.9/5.0
Behavior2/5

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

Annotations already declare openWorldHint=true and idempotentHint=true, but the description adds nothing beyond the route. It does not disclose whether a message is actually delivered, whether credentials are validated, error/rate-limit behavior, or side effects on the target channel.

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

Conciseness2/5

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

It is short with no redundancy, but the single fragment is an endpoint label rather than an informative statement; the brevity comes from under-specification rather than efficiency.

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?

With two required, undocumented parameters, no output schema, and only sparse annotations, an agent would have to guess what a successful test returns. The name conveys 'test Slack connection', but nothing in the description fills the remaining gaps.

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

Parameters1/5

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

Schema description coverage is 0% for both required parameters (webhookUrl, channel), and the description supplies no meaning for either — no expected Slack webhook URL format, whether channel is a name or ID, or how they interact.

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 is only the HTTP route 'POST /notification.testSlackConnection', which restates the tool name rather than stating what the tool does. It does not say a test message is sent to Slack, what channel/webhook is used, or what a failure means.

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

Usage Guidelines2/5

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

No guidance on when to use this versus siblings such as notification-createSlack, notification-updateSlack, or notification-testCustomConnection. The 'test' prefix implies a validation use case, but nothing explicit is stated and there are no exclusions or prerequisites.

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