Skip to main content
Glama
MCP Dokploy Online
by igoruam

notification-testNtfyConnection

Idempotent

Sends a test Ntfy notification to the specified server URL and topic using the provided access token and priority, confirming the connection works before use.

Instructions

POST /notification.testNtfyConnection

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>",
      "topic": "<topic>",
      "accessToken": "<accessToken>",
      "priority": "<priority>"
    },
    "name": "notification-testNtfyConnection"
  }
}

Input Schema

NameRequiredDescriptionDefault
topicYes
priorityYes
serverUrlYes
accessTokenYes

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 already declare openWorldHint=true and idempotentHint=true, so the agent knows a network call occurs and repeated calls are safe. The description adds nothing beyond that: it does not mention that a real push is delivered to the topic, that accessToken is used for authentication, or what a failure looks like.

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 that is under-specification rather than conciseness — a single raw route string with no sentence structure or front-loaded purpose. Nothing in it earns informational value.

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 four-required-parameter networking tool with no output schema needs the description to explain inputs and result semantics, and it supplies none of that. The definition is not sufficient for correct invocation without reading the schema and guessing.

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 four required parameters (serverUrl, topic, accessToken, priority), and the description provides no explanation of any of them. An agent gets no meaning for serverUrl format, topic naming, or the priority range beyond minimum 1.

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 endpoint string "POST /notification.testNtfyConnection", which restates the tool name rather than stating in prose that it verifies an ntfy server connection by sending a test notification. An agent must infer the verb and resource from the name alone.

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, when-not-to-use, or prerequisite guidance — nothing distinguishes this from the many sibling testConnection tools for other providers, nor from notification-createNtfy or notification-updateNtfy. The only hint is the word 'test' embedded in the name.

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