Skip to main content
Glama

read_work_item

Read-only

Retrieve a Polarion work item with its description converted to Markdown for easy reading or summarization by an LLM.

Instructions

Read a Polarion work item with its body rendered as Markdown.

Synthesis variant of get_work_item: returns the same metadata fields plus description as Markdown (converted from Polarion HTML via html_to_markdown()) instead of description_html. Use this when an LLM needs to read or summarise the body. The converter collapses Polarion-specific spans and ID anchors, so the Markdown is read-only — do NOT feed it back to update_work_item. For round-trip editing, pair get_work_item(include_description_html=True) with update_work_item(description_html=...).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesPolarion project ID.
work_item_idYesWork Item ID (e.g. 'MCPT-001').

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.
descriptionNoBody as Markdown; read-only — do NOT feed to update_work_item.
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.
Behavior5/5

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

The description discloses the conversion from Polarion HTML to Markdown, including that it collapses Polarion-specific spans and ID anchors, and explicitly states the output is read-only. This adds significant behavioral context beyond the 'readOnlyHint' annotation, which only indicates safety.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the main purpose and then provides differentiation and usage guidance. It is concise with no fluff, though it could be slightly trimmed. Each sentence serves a purpose.

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's simplicity (2 parameters, 100% schema coverage, readOnlyHint annotation, and presence of output schema), the description fully covers the tool's behavior, transformation, usage constraints, and alternatives. No gaps remain.

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 input schema covers both parameters with descriptions (100% coverage). The description does not add new semantic meaning to the parameters beyond what the schema provides, but it provides context by stating the tool's purpose. Baseline of 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 a Polarion work item with its body rendered as Markdown' and explicitly distinguishes itself from the sibling 'get_work_item' by mentioning it returns Markdown instead of HTML. The phrase 'Synthesis variant of get_work_item' further clarifies its unique purpose.

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?

The description provides explicit guidance: 'Use this when an LLM needs to read or summarise the body.' It also warns against feeding the output back to 'update_work_item' and recommends an alternative pair for round-trip editing, naming the specific parameters. This clearly differentiates when to use this tool versus alternatives.

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