Skip to main content
Glama
Sign In
OpenProject CE MCP

OpenProject CE MCP

by jtauschl
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_time_entry

Read-onlyIdempotent

Retrieve a single time entry by ID, including its full comment. Optionally cap the comment length with text_limit to control response size.

Instructions

Get a single time entry by id, including its full comment.

The comment is returned in full by default (single time entries are not truncated). Pass text_limit to cap it at that many characters; when the text is cut, comment_truncated is true and comment_length reports the real length.

Input Schema

NameRequiredDescriptionDefault
text_limitNo
time_entry_idYes

Output Schema

NameRequiredDescriptionDefault
idYes
userYes
hoursYes
commentYes
ongoingYes
projectYes
user_idNo
activityYes
end_timeYes
spent_onYes
entity_idYes
created_atYes
start_timeYes
updated_atYes
entity_nameYes
entity_typeYes
comment_lengthNo
comment_truncatedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.4.4
  2. Removedv0.4.0
  3. Changed3 schema fields changedv0.3.7
    • addedInput schema / additionalProperties
      Added value: +false
    • removedOutput schema / properties / url
      Removed value: -{
-  "title": "Url",
-  "type": "string"
-}
    • changedOutput schema / required
      Previous value: -[
-  "id",
-  "project",
-  "entity_type",
-  "entity_id",
-  "entity_name",
-  "user",
-  "activity",
-  "hours",
-  "spent_on",
-  "start_time",
-  "end_time",
-  "ongoing",
-  "comment",
-  "created_at",
-  "updated_at",
-  "url"
-]New value: +[
+  "id",
+  "project",
+  "entity_type",
+  "entity_id",
+  "entity_name",
+  "user",
+  "activity",
+  "hours",
+  "spent_on",
+  "start_time",
+  "end_time",
+  "ongoing",
+  "comment",
+  "created_at",
+  "updated_at"
+]
  4. Changed2 schema fields changedv0.3.5
    • addedOutput schema / properties / comment_length
      Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Comment Length"
+}
    • addedOutput schema / properties / comment_truncated
      Added value: +{
+  "default": false,
+  "title": "Comment Truncated",
+  "type": "boolean"
+}
  5. Addedv0.3.3
  6. Removedv0.3.0
  7. First observedv0.2.2

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive behavior. The description adds meaningful behavioral detail about comment truncation, text_limit, comment_truncated, and comment_length, though it does not discuss error or permission behavior.

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 main action is front-loaded, and the second paragraph immediately explains the default comment behavior and text_limit. There is no filler or repetition.

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?

The tool is simple, annotations cover safety, and the output schema handles return structure. The description fills the important gap around text_limit and truncation, leaving only minor details such as error behavior unstated.

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?

Schema coverage is 0%, so the description must carry parameter meaning. It thoroughly explains text_limit and the resulting truncation flags, while time_entry_id is only covered by the obvious 'by id' phrasing.

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 states a specific verb and resource: get a single time entry by id. It clearly distinguishes retrieval of one entry from list operations and notes the included full comment.

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 'single time entry by id' phrasing makes the usage context clear and implies list_time_entries is for broader retrieval. It does not explicitly name alternatives or exclusions, so it falls short of full routing guidance.

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

Deploy Server

Other Tools