Skip to main content
Glama
jtauschl

OpenProject MCP

by jtauschl
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

get_time_entry

Fetch a specific time entry by its unique ID to retrieve logged hours and booking details.

Instructions

Get a single time entry by id.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
time_entry_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
userYes
hoursYes
commentYes
ongoingYes
projectYes
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. Dates show when Glama detected each change.

  1. 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"
+]
  2. 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"
+}
  3. Addedv0.3.3
  4. Removedv0.3.0
  5. First observedv0.2.2

TDQS

A3.6/5.0
Behavior2/5

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

No annotations are provided, and the description only states the basic operation. It doesn't disclose potential errors (e.g., not found), side effects (none), or permissions. Behavioral traits are not addressed.

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 a single concise sentence with 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?

For a simple get-by-id operation, the description covers the essential purpose. It doesn't mention return value, but since output schema is present, that's acceptable. It is adequately complete for the given complexity.

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?

The schema has one required integer parameter, and the description only says 'by id'. It doesn't add meaning beyond the schema's title, so it adds minimal value.

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 operation (get) and resource (time entry) with the identifier as a parameter, effectively distinguishing it from list operations.

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

Usage Guidelines3/5

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

The description doesn't explicitly mention when to use this over list_time_entries or other getters, but the 'by id' implies retrieval of a specific resource. Given the naming convention, a user can infer, but explicit guidance would improve it.

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