Skip to main content
Glama
ni-c

ntfy-mcp

by ni-c
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Check topic access

check_topic_access
Read-onlyIdempotent

Checks if the configured credentials can subscribe to given topics, testing read access only. Note that ntfy treats read and write separately, so a write-only token may be denied here but still publish.

Instructions

Reports whether the configured credentials may SUBSCRIBE to each topic, without publishing anything.

Read the result carefully: ntfy grants read and write separately, and this endpoint tests the read side only. A write-only publishing token is denied here and can still publish perfectly well — that combination is the single most common source of confusion with ntfy.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
topicsNoTopics to check. Defaults to the first NTFY_TOPICS entry.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.3.0
    • addedOutput schema / properties / results / items / properties / not_checked
      Added value: +{
+  "const": true,
+  "type": "boolean"
+}
  2. First observedv0.2.0

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the annotations (readOnly, idempotent, non-destructive), the description transparently explains the nuanced behavior regarding read vs. write permissions and warns about a common source of confusion. This adds significant behavioral context.

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

Conciseness5/5

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

The description is concise and well-structured. The first sentence states the core purpose, and the second sentence provides an important caveat. No unnecessary information is included.

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

Completeness5/5

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

The description fully covers what the tool does, the meaning of its result, and the key nuance about read/write permissions. Since an output schema is present, no return value details are needed. The description is sufficient for a developer to understand and use the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema provides a description for the only parameter ('Topics to check. Defaults to the first NTFY_TOPICS entry.'), so schema coverage is 100%. The tool description does not add additional parameter semantics beyond what is already in the schema.

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

Purpose5/5

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

The description clearly states the tool's purpose: it reports whether the configured credentials can subscribe to topics, explicitly saying it does not publish. This verb and resource are specific, and it distinguishes itself from publishing tools by emphasizing the read-only nature.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explains that this tests only the read side and that write-only tokens will be denied here but can still publish, providing meaningful usage context. However, it does not explicitly name alternative tools or state 'use this when you need X' as opposed to alternatives.

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