ntfy-mcp

Send finished-work ping

ntfy_ping

Send a simple notification to a configured ntfy topic with optional title, message, priority, tags, icon, and delay. Use it to alert users or update statuses in real time.

Instructions

Send a simple notification to the server-configured ntfy topic.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ntfy_ping"
  }
}

Input Schema

Name	Required	Default
`icon`	No
`tags`	No
`click`	No
`delay`	No
`title`	No	Agent finished
`message`	No	Agent finished working.
`markdown`	No
`priority`	No	default

Output Schema

Name	Required	Description	Default
`url`	Yes
`topic`	Yes
`status`	Yes
`responseText`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 6, 2026

TDQS

C2.6/5.0

Behavior2/5

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

No annotations are provided, so the description carries full responsibility for behavioral disclosure. It reveals that the topic is server-configured, which is useful, but it does not mention side effects, return behavior, defaults, or what 'simple' means relative to the full parameter set.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise and front-loaded, with no wasted words. It earns its place, though it is arguably too sparse to carry the full informational burden.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with eight optional parameters, a sibling tool, and no annotations, the description is incomplete. It does not explain default behavior, how this differs from ntfy_publish, or what an agent should expect when invoking it.

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 description adds no parameter-level meaning. None of the eight parameters are mentioned or explained, leaving the agent to rely entirely on property names and defaults.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a clear verb and resource: send a notification to the server-configured ntfy topic. The title 'Send finished-work ping' adds a useful completion context. However, it does not explicitly distinguish this tool from the sibling ntfy_publish.

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 guidance on when to use ntfy_ping versus ntfy_publish. The title and the word 'simple' imply a finished-work notification, but the description does not state conditions, exclusions, or alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server