Skip to main content
Glama
MCP Dokploy Online
by igoruam

notification-createLark

Creates a Lark notification configuration in Dokploy with a webhook URL and selectable event toggles for deployments, backups, cleanup, restarts, and server threshold alerts.

Instructions

POST /notification.createLark

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-createLark"
  }
}

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.6/5.0
Behavior2/5

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

Annotations supply openWorldHint=true, which already signals an external call, and the HTTP verb hints at a create/mutate operation. Beyond that the description discloses nothing about side effects, whether a duplicate name overwrites an existing config, or what happens to the ten required flags.

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 the brevity is under-specification rather than economy: a bare route string that earns none of its space. There is no structure or front-loaded explanation of purpose.

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 ten-required-parameter creation tool with zero schema coverage and no output schema, the definition provides essentially no information an agent could use to call it correctly. This is grossly incomplete relative to the tool's complexity.

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?

Ten required parameters at 0% schema description coverage, and the description says nothing about any of them. The meanings of name, webhookUrl, and the eight boolean event toggles (appDeploy, appBuildError, dokployBackup, etc.) are left entirely to guesswork.

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 effectively a restatement of the tool name plus an HTTP route ("POST /notification.createLark"). It conveys only that a Lark notification configuration is created via POST, with no indication of what a Lark notification config contains or how it differs from notification-createSlack/Discord/Telegram siblings.

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 when-to-use guidance, no prerequisites, and no mention of alternatives such as notification-updateLark or notification-testLarkConnection. An agent must infer everything about selection from the tool 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