Skip to main content
Glama

update_document_comment

Idempotent

Toggle the resolved state of a root document comment in Polarion. Requires the short comment ID from list_document_comments and works only on top-level comments.

Instructions

Resolve or re-open a single document comment.

Sends PATCH to /projects/{p}/spaces/{s}/documents/{d}/comments/{commentId} with {"resolved": <bool>} — the only patchable attribute on a document comment. Use list_document_comments to discover the short comment ID (last segment of the full 4-part path).

Root comments only: Polarion accepts this PATCH only on top-level comments (parent_comment_id is None in list_document_comments). Calling it on a reply -- any comment with a non-null parent_comment_id -- returns HTTP 400 "Resolved field can be set only for root comments" and surfaces as RuntimeError. Filter for parent_comment_id is None before calling. There is no server-side workflow to resolve an individual reply; resolving the root marks the entire thread resolved.

This operation is idempotent: marking a comment resolved twice leaves the same server state as marking it resolved once.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesPolarion project ID.
space_idYesSpace ID (use '_default' for the default space).
document_nameYesDocument name within ``space_id``.
comment_idYesShort comment ID to update (e.g. 'c42' from ``list_document_comments``).
resolvedYesNew resolved state for the comment.
dry_runNoWhen True, return payload preview without calling Polarion.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
updatedYesTrue on a real PATCH; False on dry-run.
dry_runYesWhether this was a dry-run.
comment_idYesShort comment ID patched (e.g. 'c42'); None on dry-run.
resolvedYesThe resolved value sent (or that would be sent).
payload_previewYesJSON:API payload sent or previewed; None after real ops.
Behavior5/5

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

Beyond annotations (idempotentHint=true, destructiveHint=false), the description details the PATCH request, the constraint on root comments, the HTTP 400 error on replies, and states idempotency explicitly. No contradictions 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?

The description is well-structured with clear paragraphs. It is detailed but not overly verbose; every sentence adds information. Minor redundancy in mentioning the HTTP 400 twice could be trimmed, but overall efficient.

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 complexity (mutation, 6 params, root-comment constraint), the description covers prerequisites, error scenarios, idempotency, and the API structure. An output schema exists, so return values need not be described. Complete for an agent.

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. The description adds value by explaining that comment_id is the short ID from list_document_comments, and that resolved is a boolean. It also describes the endpoint structure, which is not in the schema.

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 starts with a clear verb+resource: 'Resolve or re-open a single document comment.' It specifies the exact action and distinguishes from sibling tools like list_document_comments and create_document_comments.

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 list_document_comments to discover the comment ID, warns that only root comments are accepted (filter by parent_comment_id is None), and describes the error behavior for replies. This helps the agent decide when to use this 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