Skip to main content
Glama

list_work_item_enum_options

Read-only

Lists valid enum options for work item fields (type, status, etc.) to ensure correct values before creating or updating work items.

Instructions

List valid enum options for a work item field of the given type.

Call this before create_work_item / update_work_item when you need to pick a value for a work item's type / status / severity / priority / custom enum field. Polarion does NOT validate these values on write -- unknown ids are stored verbatim as ghost values (priority only coerces non-numeric inputs to the project default) -- so resolve them first. This tool covers WORK ITEM fields only; document fields are surfaced via list_document_enum_options.

Returns the FULL enum set for the field on the given work item type. Workflow transitions are NOT filtered by the work item's current state; that is a separate Polarion endpoint not exposed here. work_item_type='~' returns the type-agnostic option set. An unknown work_item_type is silently treated as ~ by Polarion with no error, so verify the type id (e.g. via get_work_item) before trusting the result.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesPolarion project ID.
field_idYesField id (e.g. 'status', 'type', 'severity', 'priority', or a custom field id).
work_item_typeYesWork item type id (e.g. 'task', 'requirement'). Pass '~' for type-agnostic options.
page_sizeNoNumber of options per page (1-100, default 100).
page_numberNoPage number to retrieve (1-based, default 1).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemsYes
total_countYes
pageYes
page_sizeYes
has_moreNoTrue if more pages follow.
Behavior5/5

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

Annotations mark it readOnlyHint:true. The description adds critical context: no validation on write, returns full enum set, workflow transitions not filtered, unknown type handled silently. 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.

Conciseness4/5

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

Description is thorough and well-structured, front-loading the purpose and usage context. While every sentence adds value, it is somewhat lengthy; could be slightly more concise without losing information.

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 complexity and the presence of an output schema (not shown), the description covers all necessary aspects: what the tool does, when to use it, behavioral limits, edge cases, and how to verify results. No gaps.

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%, so baseline is 3. The description does not add substantial meaning beyond the schema; it only restates that work_item_type='~' is for type-agnostic options, which is already in the parameter description.

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?

States clearly that it lists valid enum options for work item fields, specifically distinguishes itself from the sibling tool list_document_enum_options. The verb 'list' and resource 'enum options' are precise.

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?

Explicitly advises to call this before create_work_item/update_work_item for picking enum values. Cautions that Polarion does not validate values and that unknown work_item_type is silently treated as '~', recommending verification via get_work_item. Provides clear when-to-use and exclusions.

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