Skip to main content
Glama
jtauschl

OpenProject MCP

by jtauschl
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

get_work_package_activities

Retrieve a work package's activity log, most recent first, with optional comment text limits to keep results compact. See who commented and what changed to review progress.

Instructions

Get the activity log for a work package, most recent first.

work_package_id: internal id (e.g., 952) or display_id (e.g., "PROJ-51"), not UI display number.

Comments are capped by default to keep the log compact; pass text_limit to widen (or 0-based semantics via a larger value) the per-comment cap. When a comment is cut, comment_truncated is true and comment_length reports its real length.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
text_limitNo
work_package_idYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changedv0.3.7
    • addedInput schema / additionalProperties
      Added value: +false
  2. Addedv0.3.3
  3. Removedv0.3.0
  4. Changed2 schema fields changedv0.2.3
    • addedInput schema / properties / text_limit
      Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Text Limit"
+}
    • changedOutput schema / (root)
      Previous value: -{
-  "$defs": {
-    "ActivitySummary": {
-      "properties": {
-        "comment": {
-          "anyOf": [
-            {
-              "type": "string"
-            },
-            {
-              "type": "null"
-            }
-          ],
-          "title": "Comment"
-        },
-        "created_at": {
-          "anyOf": [
-            {
-              "type": "string"
-            },
-            {
-              "type": "null"
-            }
-          ],
-          "title": "Created At"
-        },
-        "id": {
-          "title": "Id",
-          "type": "integer"
-        },
-        "type": {
-          "anyOf": [
-            {
-              "type": "string"
-            },
-            {
-              "type": "null"
-            }
-          ],
-          "title": "Type"
-        },
-        "user": {
-          "anyOf": [
-            {
-              "type": "string"
-            },
-            {
-              "type": "null"
-            }
-          ],
-          "title": "User"
-        },
-        "version": {
-          "anyOf": [
-            {
-              "type": "integer"
-            },
-            {
-              "type": "null"
-            }
-          ],
-          "title": "Version"
-        }
-      },
-      "required": [
-        "id",
-        "type",
-        "version",
-        "user",
-        "comment",
-        "created_at"
-      ],
-      "title": "ActivitySummary",
-      "type": "object"
-    }
-  },
-  "properties": {
-    "count": {
-      "title": "Count",
-      "type": "integer"
-    },
-    "results": {
-      "items": {
-        "$ref": "#/$defs/ActivitySummary"
-      },
-      "title": "Results",
-      "type": "array"
-    }
-  },
-  "required": [
-    "count",
-    "results"
-  ],
-  "title": "ActivityListResult",
-  "type": "object"
-}New value: +null
  5. First observedv0.2.2

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It explicitly explains ordering (most recent first), comment truncation behavior, how to widen the cap via text_limit, and the fields indicating truncation. This is transparent and useful.

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 compact and every sentence adds value. It is front-loaded with the primary purpose, followed by two clarifying sentences—no fluff.

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

Completeness4/5

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

Given no output schema, the description explains key output fields (comment_truncated, comment_length) and ordering. It could go further by describing the general structure of the activity log, but it is sufficiently complete for a simple getter tool.

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?

Adds significant meaning beyond the schema: explains that work_package_id accepts internal or display ID, and describes the effect of text_limit. However, the limit parameter is not mentioned, leaving a minor gap.

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?

The description clearly states the tool's purpose: "Get the activity log for a work package, most recent first." This uses a specific verb and resource, distinguishing it from sibling tools like get_work_package or get_work_package_relations.

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 useful context on when to use the tool (to retrieve activity logs) and clarifies important parameter semantics like ID formats. However, it does not explicitly exclude alternatives or state when not to use it, though the context is clear.

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/jtauschl/openproject-ce-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server