Skip to main content
Glama

create_document

Create a document in a Polarion space with unique name, title, type, and optional Markdown content. Validates inputs and configures workflow status, custom fields, and outline numbering.

Instructions

Create a document in a space.

document_name must be unique in the space — a duplicate name conflicts; check list_documents first. type/status and custom_fields keys are validated on write — resolve ids via list_document_enum_options first.

home_page_content is Markdown (greenfield only), converted to sanitized HTML. Markdown tables get native Polarion styling; a paragraph starting 'Table:' directly after a table becomes a numbered caption widget. Post-create edits round-trip raw HTML via get_document(include_home_page_content_html=True) and update_document; add work items via move_work_item_to_document.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeYesDocument type (e.g. 'req_specification', 'generic').
titleYesHuman-readable document title.
statusNoInitial workflow status (project default if omitted).
dry_runNoPreview payload without writing; guards still query Polarion.
space_idYesSpace ID ('_default' = default space).
project_idYesPolarion project ID.
auto_suspectNoFlag linked work items suspect on change.
custom_fieldsNoKeyed by Polarion field ID (copy keys from a sibling document); rich-text values as {'type':'text/html','value':...}.
document_nameYesDocument name (e.g. 'MySpecV1'); unique within space_id, appears in the document URL.
home_page_contentNoMarkdown body; converted to sanitized HTML.
uses_outline_numberingNoEnable auto outline numbers (1, 1.1, ...).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
createdYes
dry_runYes
document_nameYes
payload_previewYes
Behavior5/5

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

Annotations indicate non-readonly, non-destructive, open world. Description adds uniqueness conflict, validation on write, Markdown-to-HTML conversion with specific table/caption behavior, and dry_run preview. Discloses post-create workflow, significantly beyond 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?

Concise yet comprehensive. First sentence states purpose; subsequent sentences provide constraints, validation, and behavioral details. No redundant phrases, every sentence adds value.

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 11 parameters, 5 required, and output schema exists, description covers uniqueness, validation, Markdown specifics, round-trip editing, and references to sibling tools. No gaps for effective usage.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage 100% (baseline 3). Description adds meaning: document_name uniqueness, validation process for type/status/custom_fields, Markdown rendering details for home_page_content, and dry_run preview effect. Enhances understanding of each parameter beyond schema descriptions.

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?

Specific verb 'Create' with resource 'document in a space'. Clearly states action and context. Distinguishes from siblings by referencing related tools (list_documents, list_document_enum_options, update_document) and uniqueness constraint.

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

Usage Guidelines4/5

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

Provides guidance on prerequisites (check uniqueness with list_documents, resolve enum options with list_document_enum_options) and limitations (home_page_content only for greenfield, round-trip edits via get/update). Lacks explicit when-not-to-use but context is clear.

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