Skip to main content
Glama
MCP Dokploy Online
by igoruam

notification-testPushoverConnection

Idempotent

Tests a Pushover notification connection with a user key and API token so you can verify credentials and alert delivery before enabling notifications.

Instructions

POST /notification.testPushoverConnection

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": {
      "userKey": "<userKey>",
      "apiToken": "<apiToken>",
      "priority": "<priority>"
    },
    "name": "notification-testPushoverConnection"
  }
}

Input Schema

NameRequiredDescriptionDefault
retryNo
expireNo
userKeyYes
apiTokenYes
priorityYes

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 safety profile is partially covered. The description adds only the HTTP method, saying nothing about credential validation, external Pushover API rate limits, failure modes, or what a successful versus failed test looks like. It does not contradict the annotations.

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 brevity reflects under-specification rather than economy. The single line is an endpoint string with no front-loaded statement of purpose, so there is nothing useful to front-load.

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 five parameters, three of them required credentials, no output schema, and annotations covering only openness and idempotency, the definition leaves an agent without enough information to invoke it confidently. It should at minimum explain that it performs a live test against Pushover using the supplied credentials and how failures surface.

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 five parameters, and the description supplies no meaning for any of them. Pushover-specific semantics such as retry/expire only mattering for emergency priority, or what apiToken and userKey identify, are entirely undocumented.

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 HTTP route "POST /notification.testPushoverConnection", which restates the tool name rather than describing what the tool does. An agent can infer it tests a Pushover notification config only from the identifier, not from any stated verb or resource in prose.

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 guidance, no prerequisites, and no differentiation from the many sibling test-connection tools (testSlackConnection, testTelegramConnection, etc.). Nothing indicates whether this should be called before saving a config or only after creation.

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