Skip to main content
Glama

Mark a developer notification as read

amber_mark_notification_read
DestructiveIdempotent

Marks a developer notification as read and permanently removes it from the developer_notifications block after the user has acknowledged its content.

Instructions

Dismiss a developer notification after the user has acknowledged it. Permanently removes it from the developer_notifications block. That block is appended to a tool response ONLY WHEN there is at least one unread notification -- most responses will not contain it, and its absence means there is nothing pending, not that the feature is missing.

Side effects: deletes the notification row from the user's database. Idempotent in intent but returns code: not_found if already dismissed. Only call after the user has seen the notification content. Not rate-limited.

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

Input Schema

NameRequiredDescriptionDefault
notification_idYesPositive integer from the `id` field of a notification in `developer_notifications`. Example: if the block contains `{id: 42, message: "..."}`, pass 42. Each ID is unique and single-use.

Output Schema

NameRequiredDescriptionDefault
statusYesAlways `read`: the notification is acknowledged and will not be attached to further responses.
notification_idYesThe notification that was acknowledged.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv1.1.6
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / notification_id / exclusiveMinimum
      Added value: +0
    • addedInput schema / properties / notification_id / maximum
      Added value: +9007199254740991
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "https://json-schema.org/draft/2020-12/schema",
      +  "additionalProperties": false,
      +  "properties": {
      +    "notification_id": {
      +      "description": "The notification that was acknowledged.",
      +      "type": "number"
      +    },
      +    "status": {
      +      "const": "read",
      +      "description": "Always `read`: the notification is acknowledged and will not be attached to further responses.",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "status",
      +    "notification_id"
      +  ],
      +  "type": "object"
      +}
  2. Changed1 schema field changedv1.1.5
    • changedInput schema / properties / notification_id / description
      Previous value: -"The `id` field from a notification object in the `developer_notifications` array. Each notification has a unique positive integer ID."New value: +"Positive integer from the `id` field of a notification in `developer_notifications`. Example: if the block contains `{id: 42, message: \"...\"}`, pass 42. Each ID is unique and single-use."
  3. Changed1 schema field changedv1.1.4
    • changedInput schema / properties / notification_id / description
      Previous value: -"Numeric ID from the `developer_notifications` block in any tool response. Marks that specific notification as read and stops it from appearing. Invalid IDs return `code: not_found`."New value: +"The `id` field from a notification object in the `developer_notifications` array. Each notification has a unique positive integer ID."
  4. Changed1 schema field changedv1.1.3
    • changedInput schema / properties / notification_id / description
      Previous value: -"The numeric ID from the `developer_notifications` section that appears in every tool response when notifications are pending. Each notification has a unique ID. Only mark as read after the user has seen and acknowledged the notification content."New value: +"Numeric ID from the `developer_notifications` block in any tool response. Marks that specific notification as read and stops it from appearing. Invalid IDs return `code: not_found`."
  5. Changed1 schema field changedv1.1.1
    • changedInput schema / properties / notification_id / description
      Previous value: -"The ID from the `developer_notifications` payload."New value: +"The numeric ID from the `developer_notifications` section that appears in every tool response when notifications are pending. Each notification has a unique ID. Only mark as read after the user has seen and acknowledged the notification content."
  6. First observedv0.1.0

TDQS

A4.4/5.0
Behavior5/5

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

Adds substantial context beyond the annotations: it names the database effect (row deletion), the specific error shape on repeat calls (`code: not_found`), and that the tool is not rate-limited. It even reconciles the idempotentHint annotation with the not_found behavior ('idempotent in intent but...'), which is precisely the nuance an agent needs.

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?

Front-loads the action and consequence, then side effects and preconditions. The developer_notifications explanation is long-ish but earns its place because absence of the block is easily misread by agents. No filler sentences.

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

Completeness5/5

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

For a single-parameter destructive mutation, the description covers precondition, persistence effect, error behavior, rate limits, and the confusing absence-of-block case. With annotations and an output schema also present, nothing material is missing.

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 coverage is 100% and the schema already explains that the value is a positive integer from the `id` field, with a worked example. The description adds only the surrounding context of where that ID lives, not new parameter semantics, so baseline 3 applies.

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 and resource ('Dismiss a developer notification') and immediately specifies what that means ('Permanently removes it from the `developer_notifications` block'), so an agent knows exactly what the call does.

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?

Gives an explicit prerequisite ('Only call after the user has seen the notification content') and clarifies when the notification block is present vs absent. No sibling tool offers a comparable action, so no alternative routing is needed, but there is no guidance on what to do instead when the block is absent.

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