Skip to main content
Glama
phillipboesger

Polarion MCP Server

deleteApproval

Delete a work item approval by providing the project ID, work item ID, and user ID.

Instructions

Deletes the specified Work Item Approval.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectIdYesThe Project ID.
workItemIdYesThe Work Item ID.
userIdYesThe User ID.
Behavior2/5

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

No annotations exist, so description carries full burden. It only states 'deletes' without disclosing side effects, irreversibility, required permissions, or scope of deletion (e.g., only the approval, not associated data).

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?

Single sentence with no extraneous words. Efficiently conveys the core purpose.

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?

For a simple three-parameter delete with no output schema, the description is minimally adequate but lacks usage guidance and behavioral details that would help an agent decide correctly.

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 covers 100% of parameters with descriptions. The tool description adds no extra meaning beyond what the schema provides. Baseline 3 is appropriate.

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 the action ('deletes') and the target ('the specified work item approval'), using specific verb+resource. It distinguishes from sibling 'deleteApprovals' (plural) by implying singular deletion.

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

Usage Guidelines2/5

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

No guidance on when to use this tool vs alternatives like 'deleteApprovals' (plural) or 'deleteWorkItem'. No prerequisites or contextual usage hints provided.

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/phillipboesger/polarion-mcp'

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