Skip to main content
Glama

Get work package detail

get_work_package
Read-onlyIdempotent

Read a work package's complete details by its ID, including description, dates, custom fields, parent, and progress.

Instructions

Read one work package in full: description, dates, custom fields, parent and progress.

This is the tool to call once a search or list has given you an id, and the only way to read a work package's description text. The lock_version in the result is what update_work_package needs for a safe concurrent edit.

Returns every core field, custom_fields in the canonical [{key, name, type, value, value_ids}] shape (only fields that have a value), an available map saying whether this work package exposes dev links, meetings or file links, and any requested includes.

Pitfalls: includes are capped at 20 — a truncated children list means you should call list_work_packages(parent_id=…) for the rest, which more_via spells out verbatim. A sub-resource that 403s or 404s (module off, no permission) degrades into a notes entry instead of failing the whole read.

For the comment thread use list_work_package_comments; for attachment bytes use download_attachment; for linked PRs and commits use get_work_package_git_activity.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesWork package id — the number shown as #1234 in OpenProject. Comes from search_work_packages or list_work_packages. Instances on 17.x with semantic identifiers enabled also accept the semantic form ('PROJ-42', the row's display_id).
includeNoExtra sub-resources, fetched concurrently: 'relations', 'watchers', 'attachments', 'children', 'custom_actions'. Each is capped at 20 items and reports {truncated, total, more_via} when there are more. Ask only for what you need — every include is one more upstream request.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoWork package id.
dateNoMilestone date (ISO YYYY-MM-DD); null for non-milestones.
typeNoWork package type.
notesNoDegradation notes for this result.
authorNoCreating user.
parentNoParent work package.
statusNoStatus.
projectNoOwning project.
subjectNoSubject line.
versionNoVersion / sprint.
assigneeNoAssigned user or group.
categoryNoCategory.
childrenNoPresent only when 'children' was requested.
due_dateNoISO date (YYYY-MM-DD).
priorityNoPriority.
watchersNoPresent only when 'watchers' was requested.
availableNoFeature availability for this WP: dev links, meetings, files.
relationsNoPresent only when 'relations' was requested.
created_atNoISO 8601 UTC timestamp.
display_idNoHuman-facing id as the instance renders it. Matches the numeric id unless the instance uses semantic identifiers (17.x, e.g. 'PROJ-42'); null when the instance predates it.
start_dateNoISO date (YYYY-MM-DD).
updated_atNoISO 8601 UTC timestamp.
attachmentsNoPresent only when 'attachments' was requested.
descriptionNoDescription as markdown (raw); html is dropped.
responsibleNoAccountable user.
spent_hoursNoLogged time in hours.
lock_versionNoOptimistic-locking version; pass to update_work_package.
custom_fieldsNoAlways a list; empty when none are set.
project_phaseNoProject phase this work package sits in (16.1+, only when phases are active in the project and visible to this user); details via get_project_phase.
custom_actionsNoPresent only when 'custom_actions' was requested.
estimated_hoursNoEstimate in hours.
percentage_doneNoProgress, 0-100.
Behavior5/5

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

The description discloses rich behavioral details beyond the readOnlyHint/idempotentHint annotations: the return shape, includes cap at 20, truncation via more_via, sub-resource degradation into notes on 403/404, and lock_version semantics for concurrent edits. No contradiction with annotations.

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 longer than typical but every paragraph serves a distinct purpose: usage context, return format, pitfalls, and alternative tools. It is front-loaded with the core purpose and contains no redundant filler.

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?

The description covers usage triggers, return values, edge cases, and related tools. Combined with the fully described input schema and annotations, it gives an agent everything needed to invoke the tool correctly.

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?

Schema description coverage is 100%, with both id and include already fully documented in the input schema. The tool description adds little parameter-specific meaning beyond repeating the includes cap, so baseline 3 is appropriate.

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 'Read one work package in full' with specific content areas, and it distinguishes itself from siblings by noting it is 'the only way to read a work package's description text'. It also explicitly references related tools for other concerns.

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

Usage Guidelines5/5

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

It explicitly says when to use the tool: 'This is the tool to call once a search or list has given you an id'. It also provides direct alternatives: 'For the comment thread use list_work_package_comments; for attachment bytes use download_attachment; for linked PRs and commits use get_work_package_git_activity'.

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/kar-thik/openproject-mcp'

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