Skip to main content
Glama
MCP Dokploy Online
by igoruam

notification-createTeams

Configures a Microsoft Teams notification channel with a webhook URL and event toggles for deployments, backups, Docker cleanup, restarts, and server thresholds.

Instructions

POST /notification.createTeams

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": {
      "appBuildError": "<appBuildError>",
      "databaseBackup": "<databaseBackup>",
      "dokployBackup": "<dokployBackup>",
      "volumeBackup": "<volumeBackup>",
      "dokployRestart": "<dokployRestart>",
      "name": "<name>",
      "appDeploy": "<appDeploy>",
      "dockerCleanup": "<dockerCleanup>",
      "serverThreshold": "<serverThreshold>",
      "webhookUrl": "<webhookUrl>"
    },
    "name": "notification-createTeams"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
appDeployYes
webhookUrlYes
volumeBackupYes
appBuildErrorYes
dockerCleanupYes
dokployBackupYes
databaseBackupYes
dokployRestartYes
serverThresholdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.5/5.0
Behavior1/5

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

The only annotation is openWorldHint=true, so the description carries the full burden of disclosure and delivers essentially nothing. It never states that this is a mutating create operation, whether an existing config would be duplicated or replaced, what permissions are needed, or what the response contains. POST in the path weakly implies a write, but no behavioral trait is actually described.

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 that brevity is under-specification rather than efficiency: a single endpoint path fragment with no front-loaded purpose statement. There is nothing to trim because nothing of substance was written.

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?

For a tool requiring 10 documented-or-nothing parameters, with no output schema and only an openWorldHint annotation, the definition is far too thin. An agent would have to guess the meaning of every boolean flag and the expected webhookUrl format before it could invoke this safely.

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% across 10 required parameters, so the description must compensate and instead says nothing. Booleans like appBuildError, serverThreshold, dockerCleanup, and name/webhookUrl have no explanation of semantics, format, or defaults anywhere in the definition.

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 "POST /notification.createTeams", which restates the tool name and HTTP verb rather than stating what the tool accomplishes in domain terms. An agent can infer it creates a Teams notification channel config, but the definition adds no resource scope, no mention of which events are subscribed, and nothing to distinguish it from the many sibling create* notification tools.

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 prerequisites, and no reference to alternatives such as notification-updateTeams or notification-testTeamsConnection. The only implied usage is 'call this to create something Teams-related', which the agent must derive from the name alone.

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