Skip to main content
Glama
Foto MCP Server
by thesven

foto_dismiss_notification

Dismiss or delete a Foto notification by its notification ID to clear alerts from your notifications collection.

Instructions

Dismiss or delete an alert from your notifications collection on Foto.

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": "foto_dismiss_notification"
  }
}

Input Schema

NameRequiredDescriptionDefault
notificationIdYesThe notification ID to dismiss

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.0.1

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, and it leaves the core question unanswered: whether 'dismiss' marks the alert as read while 'delete' removes it permanently, and whether either is reversible. It also omits auth requirements and what happens when the notificationId is unknown or already dismissed.

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

Conciseness4/5

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

A single front-loaded sentence with no filler. It loses a point only because the 'dismiss or delete' hedge introduces ambiguity rather than resolving it.

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 destructive-leaning mutation tool with no annotations and no output schema, the definition says nothing about effect, reversibility, idempotency, or error behavior. The single-parameter schema keeps it simple, but the missing behavioral disclosure leaves an agent unable to predict the outcome of calling it.

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?

Schema description coverage is 100% with a single required parameter already documented as 'The notification ID to dismiss'. The description adds only that the ID belongs to the user's notifications collection on Foto, which is marginal context rather than new syntax or constraints.

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?

Names a specific verb pair (dismiss/delete) and a specific resource (an alert in the notifications collection on Foto), which clearly identifies a notification-removal operation. It is distinguishable from the read-oriented sibling foto_get_notifications, though the description never names that sibling explicitly.

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 call this versus foto_get_notifications, no prerequisite (e.g. needing the notification ID from a prior listing call), and no stated conditions or exclusions. The agent must infer the workflow entirely.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.