Skip to main content
Glama

list_document_enum_options

Read-only

Retrieve valid enum options for a document field by document type to avoid setting invalid values when updating a document.

Instructions

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

Call this before update_document when you need to pick a value for a document's status / type / custom enum field. Polarion does NOT validate these values on write -- unknown ids are stored verbatim as ghost values -- so resolve them first. This tool covers DOCUMENT fields only; work-item fields are surfaced via list_work_item_enum_options.

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesPolarion project ID.
field_idYesField id (e.g. 'status', 'type', or a custom field id).
document_typeYesDocument type id (e.g. 'systemReqSpecification'). 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?

Beyond readOnlyHint annotation, it details that Polarion does not validate values, stores ghost values, and that workflow transitions are not filtered. Also explains behavior with unknown document_type.

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?

Concise yet complete; each sentence adds critical information. Well-structured with purpose first, then usage, then behavioral notes.

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 output schema exists, description covers all needed context: purpose, preconditions, limitations, edge cases. No gaps.

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%, so baseline is 3. Description adds value by explaining document_type semantics ('~' for type-agnostic, unknown treated as '~') and verifying type id.

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 verb-resource pair: 'list valid enum options for a document field'. It differentiates from sibling tools like list_work_item_enum_options by specifying scope.

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?

Explicit guidance to call before update_document, and what it covers (status/type/custom enum). It also advises against using for work-item fields, directing to a sibling tool.

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