Skip to main content
Glama
MCP Dokploy Online
by igoruam

notification-all

Read-onlyIdempotent

Retrieves all notifications from a connected Dokploy instance so you can review deployment and infrastructure alerts in one place.

Instructions

GET /notification.all

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": "notification-all"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so the safety profile is covered externally. The description adds nothing beyond that — no indication of result volume, pagination, ordering, or whether the call can be expensive on large accounts, which is exactly the kind of context openWorldHint hints at.

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

Conciseness3/5

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

It is a single short line with no wasted words, so it is technically concise and front-loaded. However, the terseness is under-specification rather than efficiency — the line conveys a route string instead of intent.

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 zero-argument read tool with no output schema, the description should at minimum say what a notification object contains, whether all notifications or only unread ones are returned, and whether results are truncated. None of that is present, so an agent cannot predict the response.

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

Parameters4/5

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

The tool takes zero parameters with a fully closed schema (additionalProperties: false), so there is nothing for the description to disambiguate. Baseline 4 applies; no parameter explanation is needed.

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 restates the HTTP route 'GET /notification.all' rather than explaining in plain terms that it retrieves all notifications. The resource ('notification') and list operation are inferable only from the raw route string, and nothing distinguishes it from siblings such as notification-createCustom or notification-createDiscord.

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 this versus any sibling, no mention of prerequisites, scope, or whether results are user-scoped or organization-wide. The agent must infer 'list everything' purely from the '.all' suffix in the route.

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