Skip to main content
Glama
MCP Dokploy Online
by igoruam

notification-testTeamsConnection

Idempotent

Sends a test notification to a Microsoft Teams webhook URL to verify the connection and confirm that Dokploy alerts can be delivered successfully.

Instructions

POST /notification.testTeamsConnection

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>"
    },
    "name": "notification-testTeamsConnection"
  }
}

Input Schema

NameRequiredDescriptionDefault
webhookUrlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2/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, so the agent knows an external call is made and retries are safe. The description adds nothing beyond that: it does not say that a live test message is delivered to the Teams channel, what a failure looks like, or whether any state is changed.

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 but not informative; brevity here reflects under-specification rather than disciplined editing. A bare route string is not front-loaded guidance an agent can act on.

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?

For a one-parameter side-effecting test tool with no output schema and only two annotations, the description should say the tool posts a real test payload to the supplied webhook and what a success response means. None of that is present, leaving the agent to guess outcomes.

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?

Schema description coverage is 0% for the single required parameter, so the description must compensate and it does not. The name 'webhookUrl' hints at an incoming-webhook URL, but format expectations (full Teams webhook URL, secret token embedded) and validation behavior are undocumented.

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 just the HTTP route "POST /notification.testTeamsConnection", which restates the tool name rather than explaining it. An agent can infer that a Teams webhook gets exercised, but nothing states what the tool actually does (send a test message?) or how it differs from notification-createTeams.

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?

There is no when-to-use guidance, no prerequisite (e.g. a saved Teams notification config), and no exclusion pointing at notification-testSlackConnection or notification-createTeams. Usage is only implied by the shared 'test*Connection' naming pattern.

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