Backlog MCP Server

Read notification

read_notification

Retrieve detailed information about a specific Backlog notification by providing its ID to access full content and context.

Instructions

Read full notification details.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "notificationId": "<notificationId>"
    },
    "name": "read_notification"
  }
}

Input Schema

Name	Required	Description	Default
`notificationId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.4Apr 16, 2026

TDQS

C2.3/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 states the action ('read') but does not clarify if this is a safe read operation, what permissions are required, whether it marks notifications as read, or the format of returned details. This leaves significant gaps for a tool with no annotation coverage.

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?

The description is a single, efficient sentence with zero wasted words. It is appropriately sized for a simple tool, though this conciseness comes at the cost of detail.

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 tool's simplicity (1 parameter, no output schema, no annotations), the description is incomplete. It does not explain the parameter, behavioral traits, or how it differs from siblings, leaving the agent with insufficient context to use it effectively beyond basic inference.

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?

The input schema has 1 parameter with 0% description coverage, and the description does not mention 'notificationId' or explain its semantics (e.g., what valid IDs are, where to find them). It adds no meaning beyond the schema, failing to compensate for the low coverage.

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 'Read full notification details' restates the tool name 'read_notification' with minimal elaboration, making it tautological. It specifies the verb 'read' and resource 'notification details' but lacks specificity about what constitutes 'full details' or how this differs from sibling tools like 'get_notifications'.

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 such as 'get_notifications' (which likely lists notifications) or other sibling tools. The description implies usage for reading a single notification but does not specify prerequisites, context, or exclusions.

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

Deploy Server