Skip to main content
Glama

read_document

Read-only

Synthesize a Polarion document's body into flowing Markdown, combining headings, work-item descriptions, and inline prose. For read-only retrieval, not for editing.

Instructions

Render a Polarion document end-to-end as flowing Markdown.

Paginates read_document_parts internally and interleaves heading titles, embedded work-item descriptions, and inline prose into a single Markdown stream — the canonical way to read a document body. Empty placeholder paragraphs are skipped.

Output is read-only synthesis: do NOT feed it back to update_document (the rendered Markdown collapses Polarion's ID-anchored placeholder structure and the round-trip would orphan headings). Use get_document(include_homepage_content_html=True) for round-trip editing of the raw HTML source.

For metadata-only extraction (work item IDs / types / statuses / custom fields) prefer list_work_items with a SQL:(...) query — this tool always materializes the full body Markdown for every part, which is wasteful when the caller only wants a filtered list.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesPolarion project ID.
space_idYesSpace ID containing the document.
document_nameYesDocument name within the space.
page_sizeNoNumber of parts per page (1-100, default 100).
page_numberNoPage number to retrieve (1-based, default 1).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
contentYesRendered Markdown for this page.
part_countYesNumber of parts consumed on this page.
pageYesCurrent page number (1-based).
page_sizeYesMaximum number of parts per page.
total_partsYesTotal parts across the entire document.
has_moreNoTrue when more pages of parts follow.
Behavior5/5

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

Annotations declare readOnlyHint=true, and the description reinforces 'Output is read-only synthesis'. It discloses internal pagination, skipping of empty placeholders, and the structural collapse that breaks round-trips. This adds rich context beyond the annotation.

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 well-structured: starts with main purpose, then pagination and output traits, followed by warnings, and ends with alternatives. Every sentence serves a clear purpose. No fluff.

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 presence of an output schema and full parameter schema coverage, the description is remarkably thorough. It covers behavior, limitations, and relationships to 22 sibling tools, ensuring an agent can select and invoke it correctly.

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 description coverage is 100%, so baseline is 3. The description adds context by explaining that pagination uses page_size and page_number (defaults 100 and 1), but does not elaborate on project_id, space_id, or document_name beyond their schema descriptions. The added value is moderate.

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 'Render a Polarion document end-to-end as flowing Markdown' and distinguishes it from siblings like read_document_parts (paginated internally) and get_document (for round-trip editing). The verb and resource are specific, and the tool's role is unambiguous.

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 indicates it is 'the canonical way to read a document body', warns against feeding output to update_document, recommends get_document for round-trip editing, and suggests list_work_items for metadata-only extraction. Alternatives and exclusions are clearly stated.

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