Backlog MCP Server

count_notifications

Count notifications in Backlog, with options to filter by read status and organization.

Instructions

Returns count of notifications

Input Schema

TableJSON Schema

Name	Required	Description
`alreadyRead`	Yes	Whether to include already read notifications
`resourceAlreadyRead`	Yes	Whether to include notifications for already read resources
`organization`	No	Optional organization name. Use list_organizations to inspect available organizations.

Implementation Reference

src/tools/getNotificationsCount.ts:26-41 (handler)

The tool function that returns the 'count_notifications' tool definition including its handler (which calls backlog.getNotificationsCount(params)).

export const getNotificationsCountTool = (
  backlog: Backlog,
  { t }: TranslationHelper
): ToolDefinition<
  ReturnType<typeof getNotificationsCountSchema>,
  (typeof NotificationCountSchema)['shape']
> => {
  return {
    name: 'count_notifications',
    description: t(
      'TOOL_COUNT_NOTIFICATIONS_DESCRIPTION',
      'Returns count of notifications'
    ),
    schema: z.object(getNotificationsCountSchema(t)),
    outputSchema: NotificationCountSchema,
    handler: async (params) => backlog.getNotificationsCount(params),

src/tools/getNotificationsCount.ts:7-24 (schema)

Input schema definition for count_notifications: accepts 'alreadyRead' and 'resourceAlreadyRead' boolean params.

const getNotificationsCountSchema = buildToolSchema((t) => ({
  alreadyRead: z
    .boolean()
    .describe(
      t(
        'TOOL_GET_NOTIFICATIONS_COUNT_ALREADY_READ',
        'Whether to include already read notifications'
      )
    ),
  resourceAlreadyRead: z
    .boolean()
    .describe(
      t(
        'TOOL_GET_NOTIFICATIONS_COUNT_RESOURCE_ALREADY_READ',
        'Whether to include notifications for already read resources'
      )
    ),
}));

src/types/zod/backlogOutputDefinition.ts:425-427 (schema)
Output schema (NotificationCountSchema) for count_notifications: returns an object with a 'count' number field.
```
export const NotificationCountSchema = z.object({
  count: z.number(),
});
```

src/tools/tools.ts:165-174 (registration)

Registration of the count_notifications tool within the 'notifications' toolset. The tool is registered via getNotificationsCountTool(backlog, helper) on line 171.

{
  name: 'notifications',
  description: 'Tools for managing user notifications.',
  enabled: false,
  tools: [
    getNotificationsTool(backlog, helper),
    getNotificationsCountTool(backlog, helper),
    resetUnreadNotificationCountTool(backlog, helper),
    markNotificationAsReadTool(backlog, helper),
  ],

src/types/tool.ts:24-27 (helper)
The buildToolSchema helper used to construct the input schema for count_notifications.
```
export const buildToolSchema = <T extends z.ZodRawShape>(
  fn: (t: TranslationHelper['t']) => T
) => fn;
```

Tool Definition Quality

B3.1/5.0

Behavior2/5

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

No annotations are provided, so the description carries full responsibility for behavioral disclosure. It only says 'Returns count of notifications' without mentioning whether the operation is read-only, side effects, or how it handles different filtering states. This is insufficient for an agent to understand its behavior.

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?

The description is a single sentence, front-loaded with the core purpose. It is concise but could benefit from a bit more context. However, for a simple count tool, this level of brevity is acceptable.

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?

Given the low complexity (3 parameters, no output schema, no annotations), the description should at least clarify what the count includes (e.g., all notifications based on filters) and mention the return format (likely an integer). The current description is too sparse, leaving the agent to infer from parameter names and sibling context.

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?

The input schema has 100% coverage with descriptions for all three parameters. The tool description adds no additional meaning beyond what the schema already provides. Therefore, the baseline score of 3 is 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 clearly states the tool returns a count of notifications, which is a specific verb and resource. However, it does not differentiate from sibling tools like get_notifications or reset_unread_notification_count, missing an opportunity to clarify its unique role.

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?

The description does not provide explicit guidance on when to use this tool versus alternatives such as get_notifications for full details. The purpose is implied but not stated, and no exclusions or prerequisites are mentioned.

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

Install Server

Other Tools

Latest Blog Posts

Lightport: Open-Sourcing Glama's AI Gateway
By punkpeye on April 27, 2026.
open source
OpenAI
Tool Definition Quality Score (TDQS)
By punkpeye on April 3, 2026.
mcp
The Hackers Who Tracked My Sleep Cycle
By punkpeye on March 26, 2026.
security

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/nulab/backlog-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server