Polarion MCP Server

patchTestRecordAttachment

Update metadata and file data of an attachment attached to a specific test record iteration in a Polarion test run.

See more in the REST API User Guide.

TableJSON Schema

Name	Required	Description
`projectId`	Yes	The Project ID.
`testRunId`	Yes	The Test Run ID.
`testCaseProjectId`	Yes	The Testcase Project ID.
`testCaseId`	Yes	The Testcase ID.
`iteration`	Yes	The Iteration Number.
`attachmentId`	Yes	The Attachment ID.
`requestBody`	No	Attachment meta data and file data.

D1.4/5.0

Behavior1/5

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

No annotations and description only links to external docs; fails to disclose that this is a partial update operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

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

Extremely concise but useless; not front-loaded with actionable information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No explanation of what patching an attachment involves; fails to specify return values or side effects; completely inadequate.

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 describes all parameters with 100% coverage; description adds no value but also no error.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description is only a link to external documentation; does not state what the tool does. No verb or resource mentioned.

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

Usage Guidelines1/5

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

No guidance on when to use patchTestRecordAttachment vs siblings like deleteTestRecordAttachment or getTestRecordAttachment.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/phillipboesger/polarion-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server