Skip to main content
Glama
deenesjakoruzh
nulab

Backlog MCP Server

by nulab
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

reset_unread_notification_count

Clear the unread notification counter in Backlog to maintain accurate tracking of new alerts and updates.

Instructions

Reset unread notification count

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/tools/resetUnreadNotificationCount.ts:24-24 (handler)
    The handler function implementing the core tool logic: asynchronously calls the Backlog client's resetNotificationsMarkAsRead() method to reset the unread notification count.
    handler: async () => backlog.resetNotificationsMarkAsRead(),
  • src/tools/resetUnreadNotificationCount.ts:7-7 (schema)
    Defines the input schema for the tool using buildToolSchema. The schema is an empty object, indicating no input parameters are required.
    const resetUnreadNotificationCountSchema = buildToolSchema((_t) => ({}));
  • src/tools/resetUnreadNotificationCount.ts:23-23 (schema)
    Specifies the output schema as NotificationCountSchema for validation of the tool's response.
    outputSchema: NotificationCountSchema,
  • src/tools/tools.ts:158-167 (registration)
    Registers the resetUnreadNotificationCountTool within the 'notifications' toolset group in the allTools function.
      name: 'notifications',
  description: 'Tools for managing user notifications.',
  enabled: false,
  tools: [
    getNotificationsTool(backlog, helper),
    getNotificationsCountTool(backlog, helper),
    resetUnreadNotificationCountTool(backlog, helper),
    markNotificationAsReadTool(backlog, helper),
  ],
},

Tool Definition Quality

C2/5.0
Behavior1/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Reset unread notification count' implies a write/mutation operation but provides no information about what actually happens - whether this clears all notifications, sets a counter to zero, requires specific permissions, has side effects, or what the expected outcome is. The description is insufficient for understanding the tool's behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise (three words) but this brevity comes at the cost of under-specification. While it's front-loaded with the essential action, it lacks necessary context and behavioral details. The description is arguably too concise for a mutation tool with no annotations.

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 that this is a mutation tool (implied by 'reset') with no annotations and no output schema, the description is incomplete. It doesn't explain what 'reset' means operationally, what the tool actually does, what permissions might be required, or what happens after execution. For a tool that presumably modifies user notification state, this level of documentation is inadequate.

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?

The tool has zero parameters with 100% schema description coverage, so the baseline is 4. The description doesn't need to explain parameters since there are none, and the schema fully documents this. No additional parameter semantics are needed or provided.

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

Purpose2/5

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

The description 'Reset unread notification count' is a tautology that essentially restates the tool name. While it indicates the action (reset) and resource (unread notification count), it lacks specificity about what 'reset' means in this context - does it set to zero, clear all notifications, or something else? It doesn't distinguish from sibling tools like 'mark_notification_as_read' or 'count_notifications'.

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

Usage Guidelines1/5

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

The description provides no guidance about when to use this tool versus alternatives. There are several notification-related sibling tools (count_notifications, get_notifications, mark_notification_as_read, mark_watching_as_read) but the description offers no context about when this specific reset operation is appropriate versus those other notification management tools.

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