Skip to main content
Glama
Sign In
mcp-duplicati

mcp-duplicati

by aaronckj
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

dismiss_notification

Dismiss a Duplicati notification by its ID to clear alerts and reduce clutter.

Instructions

Dismiss a Duplicati notification by ID.

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": {
      "notification_id": "<notification_id>"
    },
    "name": "dismiss_notification"
  }
}

Input Schema

NameRequiredDescriptionDefault
notification_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It only states the action without revealing whether the operation is destructive, reversible, or requires authentication. The impact of dismissing a notification and any side effects are omitted.

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?

The description is a single sentence, which is concise but not structured for efficient scanning. It front-loads the action but lacks bullet points or supplementary details that could aid comprehension without adding length.

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?

Given that there is one simple parameter and no output schema, the description is incomplete. It fails to mention how to obtain notification IDs (e.g., from list_notifications), the effect of dismissal, or any confirmation behavior. This leaves the agent without sufficient context.

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 minimal value beyond the parameter name. It says 'by ID' but does not explain how to obtain the ID, its format, or any constraints. The parameter 'notification_id' remains unexplained.

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 'Dismiss a Duplicati notification by ID' clearly states the verb (dismiss), the resource (Duplicati notification), and the method (by ID). It is specific and distinguishes from sibling tools like list_notifications by indicating a targeted action on a single notification.

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?

The description provides no guidance on when to use this tool versus alternatives. It does not explain prerequisites, such as needing a valid notification ID from list_notifications, nor does it mention when dismissal is appropriate or when other tools might be needed.

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