Skip to main content
Glama
phillipboesger

Polarion MCP Server

by phillipboesger
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

postGlobalEnumeration

Creates a new global enumeration list in Polarion, spanning all projects. Use dry_run to preview the request and avoid duplicate resources.

Instructions

Creates a list of Enumerations in the Global context. Scope: spans every project (no project filter). To act on a single project, use postProjectEnumeration instead. Effect: creates a new resource on each call — calling it again with the same input creates a duplicate; it is not idempotent. 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.
requestBodyYesThe Enumeration(s) body.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field 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."
  2. Changed1 schema field changedv1.1.0
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "data": {
+      "items": {
+        "properties": {
+          "id": {
+            "example": "~/status/~",
+            "type": "string"
+          },
+          "links": {
+            "properties": {
+              "self": {
+                "example": "server-host-name/application-path/enumerations/%7E/status/%7E",
+                "type": "string"
+              }
+            },
+            "type": "object"
+          },
+          "type": {
+            "enum": [
+              "enumerations"
+            ],
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}
  3. 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 / items / properties / attributes / properties / options / items / properties / limited
      Added value: +{
+  "type": "boolean"
+}
    • addedInput schema / properties / requestBody / properties / data / items / 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"
+}
  4. First observedv1.0.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already state readOnlyHint=false and idempotentHint=false, but the description adds concrete behavior: calling again with the same input creates a duplicate, and dry-run previews are returned as error-flagged results. This goes well beyond the structured metadata and gives the agent actionable expectations.

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, then uses labeled sections for scope, effect, and tip. It is somewhat long, but each sentence adds meaningful context, especially the non-idempotency warning and the dry-run caveat.

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?

For a creation tool with complex nested input and an output schema, the description covers purpose, scope, sibling differentiation, idempotency, and safe preview behavior. It is complete enough for an agent to decide when to call it and how to 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 coverage is 100% and the schema documents both parameters, so baseline is 3. The description adds value by explaining the practical use of `dry_run` and the error-flagged preview behavior, which is not fully apparent from the schema alone.

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 states a specific verb and resource ('Creates a list of Enumerations in the Global context') and immediately clarifies scope ('spans every project'). It also names the sibling alternative `postProjectEnumeration`, so an agent can distinguish the global vs. single-project use case without inspecting schemas.

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?

It explicitly says when this tool applies ('Global context', 'no project filter') and when to prefer a sibling ('To act on a single project, use postProjectEnumeration instead'). It also warns about repeated calls creating duplicates and recommends `dry_run: true` as a safe first step.

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