Skip to main content
Glama

Acknowledge notifications

acknowledge_notifications
Destructive

Confirms delivery of a notification batch to prevent it from being returned again; call only after delivery because this action cannot be undone.

Instructions

Confirm that a batch from get_new_notifications reached the user, so it is not returned again. Call only after delivery; this cannot be undone.

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": {
      "account_alias": "<account_alias>",
      "receipt": "<receipt>",
      "context": "<context>"
    },
    "name": "acknowledge_notifications"
  }
}

Input Schema

NameRequiredDescriptionDefault
contextYesThe batch's context or its identifier.
receiptYesThe batch's receipt.
account_aliasYesLogin alias from list_accounts.

Output Schema

NameRequiredDescriptionDefault
contextYes
receiptYes
acknowledgedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.5.0
    • removedOutput schema / additionalProperties
      Removed value: -false
  2. Changed5 schema fields changedv2.3.1
    • changedInput schema / $defs / BatchContextInput / properties / alias / pattern
      Previous value: -"^(?:[^\\s\\x00-\\x1f\\x7f]|[^\\s\\x00-\\x1f\\x7f](?:[^\\s\\x00-\\x1f\\x7f]| )*[^\\s\\x00-\\x1f\\x7f])$"New value: +"^[^\\s\\x00-\\x1f\\x7f](?: *[^\\s\\x00-\\x1f\\x7f])*$"
    • addedInput schema / properties / account_alias / description
      Added value: +"Login alias from list_accounts."
    • changedInput schema / properties / account_alias / pattern
      Previous value: -"^(?:[^\\s\\x00-\\x1f\\x7f]|[^\\s\\x00-\\x1f\\x7f](?:[^\\s\\x00-\\x1f\\x7f]| )*[^\\s\\x00-\\x1f\\x7f])$"New value: +"^[^\\s\\x00-\\x1f\\x7f](?: *[^\\s\\x00-\\x1f\\x7f])*$"
    • addedInput schema / properties / context / description
      Added value: +"The batch's context or its identifier."
    • addedInput schema / properties / receipt / description
      Added value: +"The batch's receipt."
  3. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already flag this as destructive and non-read-only; the description meaningfully adds that suppression is permanent ('this cannot be undone') and that the batch will stop being returned. It does not cover behavior on stale or mismatched receipts, but the critical irreversibility is disclosed.

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

Conciseness5/5

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

Two short sentences, zero filler, with the purpose and the preconditions front-loaded. Every clause carries distinct information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Output schema exists and annotations cover the safety profile, so return values and risk need not be restated. The description is complete for correct invocation, with only minor gaps around error handling and whether repeated acknowledgements are safe.

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 receipt, context, and account_alias all documented, so the schema does the heavy lifting. The description only adds that the batch originates from a poll of get_new_notifications, which is marginal beyond the schema baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Confirm') and a specific resource (a batch from get_new_notifications), plus the effect (it is not returned again). This cleanly separates it from the sibling get_new_notifications that produces the batch.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Call only after delivery' gives an explicit when-to-call precondition tied to the polling flow. It does not discuss alternatives such as get_notification_status, but the ordering constraint is unambiguous for the intended workflow.

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