Skip to main content
Glama
MCP Dokploy Online
by igoruam

notification-testLarkConnection

Idempotent

Tests a Lark webhook URL to confirm notifications can be delivered, helping verify alert configuration before use.

Instructions

POST /notification.testLarkConnection

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

Input Schema

NameRequiredDescriptionDefault
webhookUrlYes

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 already declare openWorldHint=true and idempotentHint=true, so the network-call and repeatability profile is covered structurally. The description adds nothing beyond the annotations: it does not disclose the key side effect (a test message is likely delivered to the Lark group), failure behavior for an invalid webhook, or any rate/timeout characteristics.

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 contains no wasted words but is under-specified rather than concise; it is a route annotation, not a front-loaded explanation of the tool's 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?

With no output schema, no annotation coverage of side effects, and an undocumented required parameter, the description needed to explain the test's effect and expected outcome. It provides none of that, leaving an agent unable to predict what calling it will do.

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% and the single required parameter, webhookUrl, is documented only as a non-empty string. The description does not say what the URL should be, where to obtain it, or what format Lark expects, so it fails to compensate for the coverage gap.

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 route string "POST /notification.testLarkConnection", which restates the tool name rather than explaining the operation. An agent can infer it tests a Lark connection, but nothing states what a "test" entails (e.g. sending a probe message to the webhook) or how it differs from notification-createLark or notification-updateLark.

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 differentiation from the many sibling test tools (notification-testSlackConnection, notification-testDiscordConnection, ai-testConnection, etc.). The only implicit signal is that it targets Lark, which comes from the name, not the description.

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