Skip to main content
Glama

Get Unread Notification Count

getUnreadNotificationCount
Read-onlyIdempotent

Get the unread notification count for the authenticated user's current team, or only for one automation's notifications when automation_id is set. Each notification batch with unread members counts as 1, regardless of its member count. Requires the Notification Center feature; returns 404 when it is not enabled for the team.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "getUnreadNotificationCount"
  }
}

Input Schema

NameRequiredDescriptionDefault
team_idNoDuvo team UUID to operate on. API keys are pinned to a single team — omit this (it falls back to the key's team) or pass that same team; a different team is rejected. OAuth callers, who can span multiple teams, should pass the target team here.
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

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds genuinely non-obvious behavior: batch-level deduplication (each unread batch counts as 1 regardless of member count) and the 404 failure mode tied to feature enablement. Return format is not described, but the tool is a count and the title implies it.

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?

Three short sentences, front-loaded with the primary behavior, then the counting rule, then the prerequisite/failure mode. No restatement of the title and no filler.

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 two-optional-parameter read with a rich schema and full annotation coverage, the description covers scope, counting semantics, and the 404 prerequisite. The only minor gap is not stating the return type explicitly, which the name and title make nearly self-evident.

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%, so both team_id and automation_id already carry detailed documentation including the pinned-team constraint. The description reinforces the automation_id scoping meaning but adds no syntax or edge-case detail beyond what the schema states, making the baseline 3 appropriate.

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 names a specific verb and resource ("Get the unread notification count") and immediately scopes it to the authenticated user's current team or a single automation. It does not explicitly distinguish itself from the sibling getNotificationCounts, so the agent must infer the difference, but the resource and scope are unambiguous.

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

Usage Guidelines3/5

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

It conditions the automation-scoped mode on setting automation_id and warns that the Notification Center feature is required, returning 404 when absent. However, it gives no guidance on when to use this versus getNotificationCounts or getNotificationFeed, leaving the primary sibling choice to inference.

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