Skip to main content
Glama

Get Notification

getNotification
Read-onlyIdempotent

Get a single notification by id for the authenticated user. Requires the Notification Center feature; returns 404 when it is not enabled for the team, or when automation_id is set and the notification is not about that automation.

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": {
      "id": "<id>"
    },
    "name": "getNotification"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe notification's unique identifier
automation_idNoOnly include notifications about this automation: notifications from runs in this automation (or, with no run, for its agents), notifications for its queues, connection_broken notifications for connections its agents use, and login_broken notifications for logins its agents sign in with.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / automation_id
      Added value: +{
      +  "description": "Only include notifications about this automation: notifications from runs in this automation (or, with no run, for its agents), notifications for its queues, connection_broken notifications for connections its agents use, and login_broken notifications for logins its agents sign in with.",
      +  "format": "uuid",
      +  "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$",
      +  "type": "string"
      +}
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Beyond the readOnly/idempotent annotations, it discloses a hard prerequisite (Notification Center feature must be enabled) and specific 404 failure modes, including the automation_id mismatch case. That is real behavioral context an agent cannot get from annotations or schema alone.

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?

Two sentences, front-loaded with the core action, then the prerequisites/errors. No filler, though the 404 clause is dense enough that it merits a careful read.

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?

For a simple single-item read with full annotation coverage and 100% schema coverage, the description covers the needed call-site context: scope, prerequisite, and failure conditions. No output schema exists, so the lack of return-shape detail is a minor gap rather than a blocker.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3; the description adds value by clarifying that a non-matching automation_id produces a 404 rather than an empty result, which changes how an agent should interpret the response. It does not restate the parameter descriptions.

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?

States a specific verb and resource with scope: 'Get a single notification by id for the authenticated user.' That clearly separates it from list/feed/count siblings, though it never names an alternative explicitly.

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?

The 'single notification by id' framing makes the use case clear, and the automation_id clause explains a filtering condition. It stops short of explicit when-not guidance or pointing to getNotificationFeed/getNotificationBatch for multi-item retrieval.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources