openproject-mcp

List notifications

op_list_notifications

Retrieve your in-app notifications with filters for read status and notification reason (assigned, mentioned, watched).

Instructions

List in-app notifications for the current user. Common filters: "readIAN" ("=" "t"/"f"), "reason" ("=" "assigned"/"mentioned"/"watched").

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

Input Schema

Name	Required	Description	Default
`filters`	No
`sortBy`	No
`offset`	No
`pageSize`	No
`raw`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0May 26, 2026

TDQS

A3.9/5.0

Behavior3/5

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

No annotations provided, so description carries full burden. It describes a read operation, but doesn't explicitly state non-destructive nature or disclose pagination/rate limits. Adequate for a simple list tool.

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?

Two sentences: first states purpose clearly, second gives actionable filter examples. No redundant information, front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema, so return values undocumented. Parameters partially explained. Adequate for basic understanding but lacks details for advanced usage (e.g., default pagination, sorting behavior).

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?

Schema description coverage is 0%, so description must compensate. It explains two filter fields (readIAN, reason) with operator/values, but doesn't cover other parameters (sortBy, offset, pageSize, raw). Adds partial value beyond schema structure.

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

Purpose5/5

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

Clearly states it lists in-app notifications for the current user, with examples of common filters. Distinguishes from siblings like op_get_notification (single) and op_list_work_packages (different resource).

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

Usage Guidelines4/5

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

Provides common filter examples implying typical use cases, but lacks explicit guidance on when to use vs alternatives (e.g., op_get_notification, op_mark_notification_read) or when not to use.

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