Skip to main content
Glama
phillipboesger

Polarion MCP Server

by phillipboesger
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

patchProjectEnumeration

Idempotent

Update an enumeration within a specific Polarion project, with an optional dry-run to preview changes before applying.

Instructions

Updates the specified Enumeration in the Project context. Scope: one project (requires a project ID). To act across all projects, use patchGlobalEnumeration instead. Effect: idempotent — calling it again with the same input leaves the resource in the same end state, with no additional side effects. Tip: set dry_run: true first to preview the exact request Polarion would receive, without changing anything. On tools with a typed output schema, this preview is returned as an error-flagged result since it is not real tool output -- read the text content regardless of that flag.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dry_runNoIf true, validates the request and returns the exact request that would be sent to Polarion — with the Authorization header redacted and any binary payload summarized by byte length — without actually sending it.
enumNameYesThe Enumeration Name.
projectIdYesThe Polarion project ID (its URL segment, e.g. `myproject`), case-sensitive. Required to scope the request to one project; call getProjects to list valid IDs.
targetTypeYesIdentifies the target resource type this operation applies to (e.g. `workitem`). Use `~` (no quotes) to mean no specific target type.
enumContextYesThe Enumeration context. (Allowed values are '~', 'plans', 'testing' and 'documents'. Use '~' for Work Item or general enumerations.)
requestBodyYesThe Enumeration(s) body.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.2.0
    • changedInput schema / properties / dry_run / description
      Previous value: -"If true, validate and return the request that would be sent without calling Polarion."New value: +"If true, validates the request and returns the exact request that would be sent to Polarion — with the Authorization header redacted and any binary payload summarized by byte length — without actually sending it."
    • changedInput schema / properties / projectId / description
      Previous value: -"The Project ID."New value: +"The Polarion project ID (its URL segment, e.g. `myproject`), case-sensitive. Required to scope the request to one project; call getProjects to list valid IDs."
    • changedInput schema / properties / targetType / description
      Previous value: -"The Enumeration target type. (Use '~' when there is no specific type for the enumeration.)"New value: +"Identifies the target resource type this operation applies to (e.g. `workitem`). Use `~` (no quotes) to mean no specific target type."
  2. Changed3 schema fields changed
    • addedInput schema / properties / dry_run
      Added value: +{
+  "description": "If true, validate and return the request that would be sent without calling Polarion.",
+  "type": "boolean"
+}
    • addedInput schema / properties / requestBody / properties / data / properties / attributes / properties / options / items / properties / limited
      Added value: +{
+  "type": "boolean"
+}
    • addedInput schema / properties / requestBody / properties / data / properties / attributes / properties / options / items / properties / linkRules
      Added value: +{
+  "items": {
+    "properties": {
+      "fromTypes": {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "sameType": {
+        "type": "boolean"
+      },
+      "toTypes": {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      }
+    },
+    "type": "object"
+  },
+  "type": "array"
+}
  3. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare idempotentHint and destructiveHint, but the description adds valuable context by spelling out the idempotent effect ('same end state, no additional side effects') and the dry_run preview behavior, including the nuance that previews are returned as error-flagged results. It does not duplicate the safety profile entirely; it goes beyond the annotations with the dry_run explanation.

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 front-loaded with the core purpose and scope, then adds the sibling alternative, idempotency, and the dry_run tip. Each sentence adds some value, though the idempotency statement partially duplicates the idempotentHint annotation, and the error-flag explanation could be trimmed. Still, it is well-organized and appropriately sized for a complex tool.

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

Completeness3/5

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

The description is thorough for usage and safety, but since the tool has no output schema, it would benefit from mentioning what the successful response contains (e.g., the updated enumeration). The dry_run tip partially addresses preview, but a patch operation normally returns a representation of the updated resource, and that is not disclosed. Given the nested request body complexity, this is a notable gap.

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 description coverage is 100%, so the baseline is 3. The description does not add material parameter-level meaning beyond what the schema describes; it only reiterates the need for a project ID, which the schema already states. The dry_run tip is behavioral rather than parameter semantics.

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?

States a specific verb ('Updates'), resource ('Enumeration'), and scope ('in the Project context'). It also differentiates from the global variant by naming patchGlobalEnumeration and clarifying the project-ID requirement. An agent can distinguish it from siblings like postProjectEnumeration or deleteProjectEnumeration without opening the schema.

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 tells when to use this tool (project-scoped updates) and when to use the alternative: 'To act across all projects, use patchGlobalEnumeration instead.' It also provides a practical tip about using dry_run to preview the request, which helps the agent choose the safe path first.

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

Deploy Server

Other Tools