Backlog MCP Server

Get notifications

get_notifications

Retrieve recent Backlog notifications to monitor project updates, issues, and pull requests. Filter results by ID range, count, or order to track activity.

Instructions

Get recent Backlog notifications.

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": "get_notifications"
  }
}

Input Schema

Name	Required	Description	Default
`minId`	No
`maxId`	No
`count`	No
`order`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.4Apr 16, 2026

TDQS

C2.4/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states it gets notifications but doesn't describe what 'recent' means, whether results are paginated, the format of returned data, or any limitations (e.g., rate limits, authentication needs). This is inadequate for a tool with 4 parameters and no output schema.

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, efficient sentence with no wasted words. It's appropriately sized for a simple tool, though it could be more informative without sacrificing conciseness.

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 complexity (4 parameters, 0% schema coverage, no output schema, no annotations), the description is incomplete. It doesn't explain what the tool returns, how parameters interact, or behavioral traits like pagination or error handling. The agent would struggle to use this effectively without additional context.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate by explaining parameters. It mentions 'recent' which loosely relates to minId/maxId/order parameters but doesn't define their semantics (e.g., that minId/maxId filter by notification ID, count limits results, order sorts by ID). The description adds minimal value beyond the bare schema.

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?

The description states the verb 'Get' and resource 'recent Backlog notifications', which clarifies the basic purpose. However, it's vague about what 'recent' means (time-based or ID-based) and doesn't distinguish this tool from the sibling 'read_notification' tool, leaving ambiguity about their different use cases.

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 is provided on when to use this tool versus alternatives like 'read_notification'. The description mentions 'recent' notifications but doesn't explain how this differs from other notification-related tools or when to choose this over others, leaving the agent without usage context.

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

Deploy Server