Skip to main content
Glama
nulab

Backlog MCP Server

get_notifications

Retrieve notifications from Backlog with optional filters by ID range, count, sort order, and organization.

Instructions

Returns list of notifications

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
minIdNoMinimum notification ID
maxIdNoMaximum notification ID
countNoNumber of notifications to retrieve
orderNoSort order
organizationNoOptional organization name. Use list_organizations to inspect available organizations.

Implementation Reference

  • The handler function that executes the 'get_notifications' tool logic. It calls backlog.getNotifications() with minId, maxId, count, order parameters.
    export const getNotificationsTool = (
      backlog: Backlog,
      { t }: TranslationHelper
    ): ToolDefinition<
      ReturnType<typeof getNotificationsSchema>,
      (typeof NotificationSchema)['shape']
    > => {
      return {
        name: 'get_notifications',
        description: t(
          'TOOL_GET_NOTIFICATIONS_DESCRIPTION',
          'Returns list of notifications'
        ),
        schema: z.object(getNotificationsSchema(t)),
        outputSchema: NotificationSchema,
        handler: async ({ minId, maxId, count, order }) =>
          backlog.getNotifications({
            minId,
            maxId,
            count,
            order,
          }),
      };
    };
  • Input schema for get_notifications tool defining optional parameters: minId (number), maxId (number), count (number), order (enum 'asc'|'desc').
    const getNotificationsSchema = buildToolSchema((t) => ({
      minId: z
        .number()
        .optional()
        .describe(t('TOOL_GET_NOTIFICATIONS_MIN_ID', 'Minimum notification ID')),
      maxId: z
        .number()
        .optional()
        .describe(t('TOOL_GET_NOTIFICATIONS_MAX_ID', 'Maximum notification ID')),
      count: z
        .number()
        .optional()
        .describe(
          t('TOOL_GET_NOTIFICATIONS_COUNT', 'Number of notifications to retrieve')
        ),
      order: z
        .enum(['asc', 'desc'])
        .optional()
        .describe(t('TOOL_GET_NOTIFICATIONS_ORDER', 'Sort order')),
    }));
  • Output schema (NotificationSchema) for the get_notifications tool, defining the shape of returned notification objects including id, alreadyRead, reason, resourceAlreadyRead, project, issue, comment, pullRequest, pullRequestComment, sender, and created.
    export const NotificationSchema = z.object({
      id: z.number(),
      alreadyRead: z.boolean(),
      reason: z.number(),
      resourceAlreadyRead: z.boolean(),
      project: ProjectSchema.optional(),
      issue: IssueSchema.optional(),
      comment: IssueCommentSchema.optional(),
      pullRequest: PullRequestSchema.optional(),
      pullRequestComment: PullRequestCommentSchema.optional(),
      sender: UserSchema,
      created: z.string(),
    });
  • Registration of get_notifications tool in the 'notifications' toolset within allTools(). The toolset groups notification-related tools together.
    {
      name: 'notifications',
      description: 'Tools for managing user notifications.',
      enabled: false,
      tools: [
        getNotificationsTool(backlog, helper),
        getNotificationsCountTool(backlog, helper),
        resetUnreadNotificationCountTool(backlog, helper),
        markNotificationAsReadTool(backlog, helper),
      ],
    },
  • Import of getNotificationsTool from the getNotifications module, linking the tool definition to the tools registry.
    import { getNotificationsTool } from './getNotifications.js';
Behavior2/5

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

With no annotations, the description carries full burden but only says 'returns list of notifications'. No mention of whether it's read-only, state changes, rate limits, or other behavioral traits.

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?

Single sentence, concise without filler. Could be slightly more informative without sacrificing brevity.

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?

Lacks explanation of return format, pagination, or default behavior. Given 5 parameters and no output schema or annotations, the description is insufficient for an agent to understand the full 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?

Input schema has 100% coverage with clear descriptions for all 5 parameters. The tool description adds no additional meaning beyond the schema, so baseline score applies.

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

Purpose3/5

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

Description states 'Returns list of notifications', which is a clear verb+resource but lacks specificity about what type of notifications or how they are filtered. It does not distinguish from sibling tools like count_notifications or mark_notification_as_read.

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

Usage Guidelines2/5

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

No guidance provided on when to use this tool versus alternatives. No context on prerequisites or typical use cases.

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

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