Skip to main content
Glama
MCP Dokploy Online
by igoruam

notification-updateLark

Idempotent

Update an existing Lark notification configuration by ID, including its webhook URL and event triggers for deployment, backup, build, cleanup, and server alerts.

Instructions

POST /notification.updateLark

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

Input Schema

NameRequiredDescriptionDefault
nameNo
larkIdYes
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.5/5.0
Behavior1/5

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

Annotations provide idempotentHint=true and openWorldHint=true, but the description adds nothing about what changes, permission requirements, or effects on the existing Lark notification. It carries none of its own behavioral burden.

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 single line is short but conveys almost nothing, so it fails through under-specification rather than verbosity. A route string is not a description.

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?

A 13-parameter mutation tool with no output schema and no parameter documentation needs a substantive description; this supplies none. An agent cannot determine what a call does, what the flags mean, or when to prefer a sibling tool.

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 13 parameters, including two required ones (notificationId, larkId) and numerous boolean event flags (appDeploy, databaseBackup, serverThreshold, etc.). The description adds no meaning to any of them, leaving an agent to guess which fields are updated and what each toggle enables.

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 raw route string "POST /notification.updateLark", which restates the tool name and HTTP method. It implies updating a Lark notification configuration but never states what is updated or how it differs from notification-createLark.

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 mention of alternatives such as notification-createLark or notification-testLarkConnection. The 'update' in the endpoint path is the only, and purely implied, usage signal.

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