Skip to main content
Glama

get_work_item

Read-only

Retrieve full details of a Polarion work item, including optional HTML description for lossless round-trip editing.

Instructions

Get full details of a single Polarion work item.

With include_description_html=True the description_html field carries the raw Polarion HTML body — the exact shape that round-trips through update_work_item(description_html=...) losslessly. Only feed it back when this flag was True (a False read blanks the field, and the update tool treats "" as leave unchanged).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesPolarion project ID.
work_item_idYesWork Item ID (e.g. 'MCPT-001').
include_description_htmlNoWhen True, fill ``description_html`` with raw HTML for round-trip editing.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesWork Item ID (e.g. 'MCPT-001').
titleYesWork Item title.
typeYesWork Item type (e.g. 'requirement', 'testCase').
statusYesWorkflow status (e.g. 'draft', 'approved').
priorityNoPriority value as a string (e.g. '90.0'); empty when unset.
updatedNoISO-8601 last-modified timestamp; empty when unreported.
space_idNoContaining document's space; empty when free-floating.
document_nameNoContaining document name; empty when free-floating.
assignee_idsNoShort user IDs of assignees; empty list when unassigned.
description_htmlNoRaw Polarion HTML body; empty unless the read flag was True.
project_idYesProject that contains this work item.
author_idNoShort user ID of the author; empty when unreported.
createdNoISO-8601 creation timestamp; empty when unreported.
resolutionNoResolution outcome (e.g. 'fixed'); empty when unresolved.
severityNoSeverity classification (e.g. 'critical'); empty for non-defects.
outline_numberNoHierarchical position (e.g. '1.2.3'); empty outside a document.
hyperlinksNoExternal hyperlinks attached to this work item.
custom_fieldsNoProject-defined custom fields keyed by field ID.
Behavior4/5

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

The description adds behavioral context beyond the readOnlyHint annotation: it explains the round-trip behavior of description_html, the impact of the flag on the field, and the interaction with update_work_item. This is valuable for the agent.

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 brief and to the point. It starts with the core purpose, then efficiently explains the key parameter behavior with a warning. No unnecessary words or repetition.

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?

Given the tool has an output schema (so description need not cover returns) and annotations, the description fully explains the critical behavioral nuance of the include_description_html parameter. It provides everything needed for correct invocation.

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 100%, providing a baseline of 3. The description adds significant meaning for include_description_html, explaining its role in round-trip editing and warning about reusing the value. For the other parameters, the schema descriptions suffice.

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 'Get full details of a single Polarion work item' with a specific verb and resource. It distinguishes from siblings like list_work_items (list) and read_work_item (which likely returns less detail) by implying 'full details' and the special round-trip capability.

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 gives detailed guidance on when to set include_description_html=True and the consequences, but does not explicitly state when to use this tool versus alternatives like read_work_item. The 'full details' distinction is implied but not spelled out.

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/devemberx/mcp-server-polarion'

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