Skip to main content
Glama
MCP Dokploy Online
by igoruam

notification-one

Read-onlyIdempotent

Fetches a specific Dokploy notification by ID so you can review alerts or troubleshoot deployment events.

Instructions

GET /notification.one

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": {
      "notificationId": "<notificationId>"
    },
    "name": "notification-one"
  }
}

Input Schema

NameRequiredDescriptionDefault
notificationIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=true, so the safety profile is covered. The description adds no behavioral context of its own — no statement of what happens on a missing ID, whether the response is a single object, or what the openWorld call entails. It is consistent with, but does not enrich, 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?

Brevity here is under-specification rather than conciseness: five words that carry the route path but no actionable meaning for an agent. There is nothing superfluous, but also nothing front-loaded beyond the endpoint literal.

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 single-parameter lookup with no output schema, the description should at minimum confirm the return shape and ID sourcing. Neither is present, and the 0% parameter coverage leaves the one input undefined, so an agent cannot call this confidently from the definition alone.

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

Parameters2/5

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

Schema description coverage is 0% and the single required parameter (notificationId) is undocumented anywhere. The description does not explain whether the ID is the notification's own identifier, nor its format or sourcing, so it fails to compensate for the coverage gap.

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 a raw HTTP route ("GET /notification.one") that largely restates the tool name rather than stating what the tool does in agent-facing terms. The HTTP verb plus singular resource form weakly implies "fetch one notification by ID," but that inference has to be supplied by the reader, and nothing distinguishes it from any other *-one sibling beyond the resource noun embedded in the name.

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 tool versus the many sibling single-resource getters, and no prerequisites or conditions are named. Any usage context (e.g., 'after listing notifications, fetch full detail for one') is left entirely implicit.

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