Skip to main content
Glama
MCP Dokploy Online
by igoruam

notification-testGotifyConnection

Idempotent

Tests a Gotify server connection using a server URL, app token, and priority to verify notifications can be delivered before configuring alerts.

Instructions

POST /notification.testGotifyConnection

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": {
      "serverUrl": "<serverUrl>",
      "appToken": "<appToken>",
      "priority": "<priority>"
    },
    "name": "notification-testGotifyConnection"
  }
}

Input Schema

NameRequiredDescriptionDefault
appTokenYes
priorityYes
serverUrlYes
decorationNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.3/5.0
Behavior1/5

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

Annotations only declare openWorldHint=true and idempotentHint=true; they say nothing about whether this performs an outbound network call to the supplied serverUrl, what a failure looks like, or whether any state changes. The description adds zero behavioral context beyond the route string, leaving the mutation/verification semantics and error behavior undisclosed.

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 brevity here comes from omission rather than efficiency. A single route token is not front-loaded information an agent can 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 tool with four parameters, three of them required and none documented, plus no output schema, the description is entirely inadequate. It should at minimum explain the outbound connectivity test and what the parameters represent.

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% for four parameters, including three required ones (serverUrl, appToken, priority) and an undocumented 'decoration' boolean. The description provides no meaning for any of them, so the agent must guess at formats, URL expectations, or the effect of priority and decoration.

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 just the HTTP route 'POST /notification.testGotifyConnection', which restates the tool name rather than describing intent. An agent can infer it tests a Gotify notification target, but there is no verb+resource explanation, no statement of what 'test' means, and no differentiation from sibling test tools beyond the embedded service name.

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?

No when-to-use, when-not-to-use, or prerequisite guidance is given. Nothing tells the agent to prefer this over notification-testCustomConnection or notification-createGotify, nor that a Gotify configuration must exist first.

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