Retrieve the current user's active reminders across all work packages to track upcoming work; requires OpenProject 16.1+.
List the current user's active reminders across all work packages. Requires OpenProject 16.1+.
| Name | Required | Description | Default |
|---|---|---|---|
| select | No | Fields to return; a requested unset field comes back as null. Allowed: creator, id, note, remind_at, work_package_id. |
Changes observed during successful MCP inspections.
v0.4.4v0.4.0v0.3.7Input schema / additionalPropertiesAdded value: +falsev0.3.3v0.3.0v0.2.3Output schema / (root)Previous value: -{
- "$defs": {
- "ReminderSummary": {
- "properties": {
- "creator": {
- "anyOf": [
- {
- "type": "string"
- },
- {
- "type": "null"
- }
- ],
- "title": "Creator"
- },
- "id": {
- "title": "Id",
- "type": "integer"
- },
- "note": {
- "anyOf": [
- {
- "type": "string"
- },
- {
- "type": "null"
- }
- ],
- "title": "Note"
- },
- "remind_at": {
- "anyOf": [
- {
- "type": "string"
- },
- {
- "type": "null"
- }
- ],
- "title": "Remind At"
- },
- "url": {
- "anyOf": [
- {
- "type": "string"
- },
- {
- "type": "null"
- }
- ],
- "title": "Url"
- },
- "work_package_id": {
- "anyOf": [
- {
- "type": "integer"
- },
- {
- "type": "null"
- }
- ],
- "title": "Work Package Id"
- }
- },
- "required": [
- "id",
- "remind_at",
- "note",
- "work_package_id",
- "creator",
- "url"
- ],
- "title": "ReminderSummary",
- "type": "object"
- }
- },
- "properties": {
- "count": {
- "title": "Count",
- "type": "integer"
- },
- "results": {
- "items": {
- "$ref": "#/$defs/ReminderSummary"
- },
- "title": "Results",
- "type": "array"
- }
- },
- "required": [
- "count",
- "results"
- ],
- "title": "ReminderListResult",
- "type": "object"
-}New value: +nullv0.2.2Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already establish read-only, idempotent, non-destructive behavior. The description adds useful behavioral context with the active-reminder filter and OpenProject 16.1+ requirement, but it does not cover ordering, pagination, or return behavior.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two concise sentences, front-loaded with the core purpose and followed by a necessary version prerequisite. No wasted wording.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple zero-required-parameter list tool with annotations covering safety, the description supplies the main scope and version requirement. The allowed return fields are documented in the schema, though return ordering or pagination is not described.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, and the single optional select parameter is fully documented in the schema. The description adds no parameter-specific semantics, so baseline 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource: listing the current user's active reminders, scoped across all work packages. The scope and filter are clear enough to distinguish it from create/update/delete reminder siblings.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies the usage context by saying it lists the current user's active reminders across all work packages, but it does not explicitly state when to use this tool versus related reminder mutation tools or other work-package listing tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.