Skip to main content
Glama
jtauschl

OpenProject MCP

by jtauschl
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

list_time_entries

Retrieve time entries from OpenProject using optional filters for project, work package, user, and date range. Paginate through results with offset until the provided next_offset is null.

Instructions

List time entries with optional project, work package, user, and date filters.

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

limit is capped at OPENPROJECT_MAX_PAGE_SIZE (default 50); pass the returned next_offset as the next call's offset to page past the cap. total is only the count of allowed time entries returned on THIS page, not a full count of all matches — the search stops as soon as it has enough, so an exact total would need an extra full walk. Page until next_offset is null.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
userNo
limitNo
offsetNo
projectNo
spent_on_toNo
spent_on_fromNo
work_package_idNo

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. Changed1 schema field changedv0.2.3
    • changedOutput schema / (root)
      Previous value: -{
-  "$defs": {
-    "TimeEntrySummary": {
-      "properties": {
-        "activity": {
-          "anyOf": [
-            {
-              "type": "string"
-            },
-            {
-              "type": "null"
-            }
-          ],
-          "title": "Activity"
-        },
-        "comment": {
-          "anyOf": [
-            {
-              "type": "string"
-            },
-            {
-              "type": "null"
-            }
-          ],
-          "title": "Comment"
-        },
-        "created_at": {
-          "anyOf": [
-            {
-              "type": "string"
-            },
-            {
-              "type": "null"
-            }
-          ],
-          "title": "Created At"
-        },
-        "end_time": {
-          "anyOf": [
-            {
-              "type": "string"
-            },
-            {
-              "type": "null"
-            }
-          ],
-          "title": "End Time"
-        },
-        "entity_id": {
-          "anyOf": [
-            {
-              "type": "integer"
-            },
-            {
-              "type": "null"
-            }
-          ],
-          "title": "Entity Id"
-        },
-        "entity_name": {
-          "anyOf": [
-            {
-              "type": "string"
-            },
-            {
-              "type": "null"
-            }
-          ],
-          "title": "Entity Name"
-        },
-        "entity_type": {
-          "anyOf": [
-            {
-              "type": "string"
-            },
-            {
-              "type": "null"
-            }
-          ],
-          "title": "Entity Type"
-        },
-        "hours": {
-          "anyOf": [
-            {
-              "type": "string"
-            },
-            {
-              "type": "null"
-            }
-          ],
-          "title": "Hours"
-        },
-        "id": {
-          "title": "Id",
-          "type": "integer"
-        },
-        "ongoing": {
-          "title": "Ongoing",
-          "type": "boolean"
-        },
-        "project": {
-          "anyOf": [
-            {
-              "type": "string"
-            },
-            {
-              "type": "null"
-            }
-          ],
-          "title": "Project"
-        },
-        "spent_on": {
-          "anyOf": [
-            {
-              "type": "string"
-            },
-            {
-              "type": "null"
-            }
-          ],
-          "title": "Spent On"
-        },
-        "start_time": {
-          "anyOf": [
-            {
-              "type": "string"
-            },
-            {
-              "type": "null"
-            }
-          ],
-          "title": "Start Time"
-        },
-        "updated_at": {
-          "anyOf": [
-            {
-              "type": "string"
-            },
-            {
-              "type": "null"
-            }
-          ],
-          "title": "Updated At"
-        },
-        "url": {
-          "title": "Url",
-          "type": "string"
-        },
-        "user": {
-          "anyOf": [
-            {
-              "type": "string"
-            },
-            {
-              "type": "null"
-            }
-          ],
-          "title": "User"
-        }
-      },
-      "required": [
-        "id",
-        "project",
-        "entity_type",
-        "entity_id",
-        "entity_name",
-        "user",
-        "activity",
-        "hours",
-        "spent_on",
-        "start_time",
-        "end_time",
-        "ongoing",
-        "comment",
-        "created_at",
-        "updated_at",
-        "url"
-      ],
-      "title": "TimeEntrySummary",
-      "type": "object"
-    }
-  },
-  "properties": {
-    "count": {
-      "title": "Count",
-      "type": "integer"
-    },
-    "limit": {
-      "title": "Limit",
-      "type": "integer"
-    },
-    "next_offset": {
-      "anyOf": [
-        {
-          "type": "integer"
-        },
-        {
-          "type": "null"
-        }
-      ],
-      "title": "Next Offset"
-    },
-    "offset": {
-      "title": "Offset",
-      "type": "integer"
-    },
-    "results": {
-      "items": {
-        "$ref": "#/$defs/TimeEntrySummary"
-      },
-      "title": "Results",
-      "type": "array"
-    },
-    "total": {
-      "title": "Total",
-      "type": "integer"
-    },
-    "truncated": {
-      "title": "Truncated",
-      "type": "boolean"
-    }
-  },
-  "required": [
-    "offset",
-    "limit",
-    "total",
-    "count",
-    "next_offset",
-    "truncated",
-    "results"
-  ],
-  "title": "TimeEntryListResult",
-  "type": "object"
-}New value: +null
  5. First observedv0.2.2

TDQS

A4.2/5.0
Behavior4/5

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

While no annotations are present, the description compensates by disclosing critical behavioral details: the meaning of 'total' (page-limited), the early-termination optimization, and the necessity to page via 'next_offset'. This goes beyond the bare minimum, though it could still explain error cases or rate limits. However, the substantial page-walk disclosure deserves high marks.

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?

Every sentence earns its place. The description front-loads the purpose, then dedicates a dense but readable paragraph to pagination gotchas. No fluff, no repetition, and it stays focused on what's not obvious.

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

Completeness5/5

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

For a read-only tool with rich parameters and no output schema, the description covers the critical context: parameter meanings, pagination, and value semantics (total). The only missing piece is clarifying the remaining undocumented params, but the complexity is high and the description handles the hardest parts well.

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?

With 0% schema coverage and 7 parameters, the description carries the full burden. It clarifies 'work_package_id' (internal vs display ID), 'limit' (capped at OPENPROJECT_MAX_PAGE_SIZE), and 'offset' (use next_offset). It misses explaining 'spent_on_from', 'spent_on_to', 'user', and 'project' formats, so it's not perfect, but what's covered is explained precisely.

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

Purpose4/5

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

The description opens with a clear statement: 'List time entries with optional project, work package, user, and date filters.' It uses a specific verb and resource, and the mention of filters helps distinguish it from sibling tools like 'get_time_entry' (singular). However, it doesn't explicitly name a sibling as an alternative, so it falls short of a 5.

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?

The description implicitly communicates usage via the filtering capability and pagination workaround. However, it doesn't explicitly state when to use this over alternatives or give exclusions. The alternative to use for filtered searches is implied but not named, so it misses the 'explicit alternative' bar.

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