Skip to main content
Glama
MCP Dokploy Online
by igoruam

notification-updateTeams

Idempotent

Updates Microsoft Teams notification settings in Dokploy, including webhook URL, name, and event triggers such as deployments, backups, and server alerts.

Instructions

POST /notification.updateTeams

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": {
      "notificationId": "<notificationId>",
      "teamsId": "<teamsId>"
    },
    "name": "notification-updateTeams"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
teamsIdYes
appDeployNo
webhookUrlNo
volumeBackupNo
appBuildErrorNo
dockerCleanupNo
dokployBackupNo
databaseBackupNo
dokployRestartNo
notificationIdYes
organizationIdNo
serverThresholdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.8/5.0
Behavior2/5

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

Annotations declare openWorldHint=true and idempotentHint=true but there are no destructive/readOnly hints, and the description adds nothing about permission requirements, whether omitted fields are preserved (partial vs full replace), or side effects of changing a webhook target. The 'POST' verb at least implies a mutating call consistent with the annotations, but no real behavioral context is disclosed.

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?

The string is short but that brevity reflects under-specification rather than economy of expression. There is no structure, no front-loaded purpose statement, and nothing for the reader to act on.

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 13-parameter mutation tool with 0% schema coverage and no output schema, the description supplies none of the missing context. An agent would have to guess at nearly every field's meaning and at the tool's mutation semantics.

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?

The schema has 13 parameters with 0% description coverage, and the description names none of them. There is no explanation of what the many event-toggle booleans (appDeploy, dockerCleanup, databaseBackup, serverThreshold, etc.) do, nor of the relationship between notificationId, teamsId, organizationId, and webhookUrl.

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.updateTeams", which restates the tool name rather than describing what the tool actually does. An agent can infer 'update a Teams notification target' from the name alone, but the description contributes nothing beyond that and does not differentiate it from sibling update 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?

No when-to-use guidance is given: nothing says whether this edits an existing Teams notification config, when to choose it over notification-createTeams, or what prerequisites exist. The only signal is the implicit 'update' in the path, which the agent must supply itself.

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