Skip to main content
Glama
marco-looy

Pega DX MCP Server

by marco-looy

delete_case_tag

Remove a specific tag from a Pega case by providing the case ID and tag ID to manage case organization and metadata.

Instructions

Delete a specific tag from a case by case ID and tag ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
caseIDYesCase ID. Example: "MYORG-APP-WORK C-1001". Complete identifier including spaces."OSIEO3-DOCSAPP-WORK T-561003". a complete case identifier including spaces and special characters.
tagIDYesTag ID to be deleted from the case. This is the unique identifier of the specific tag to remove.
sessionCredentialsNoOptional session-specific credentials. If not provided, uses environment variables. Supports two authentication modes: (1) OAuth mode - provide baseUrl, clientId, and clientSecret, or (2) Token mode - provide baseUrl and accessToken.

Implementation Reference

  • The execute method that performs the tool's core logic: validates inputs, initializes session, handles errors, and calls pegaClient.deleteCaseTag to delete the tag from the case.
    async execute(params) {
      const { caseID, tagID } = params;
      let sessionInfo = null;
    
      try {
        sessionInfo = this.initializeSessionConfig(params);
    
        // Validate required parameters using base class
        const requiredValidation = this.validateRequiredParams(params, ['caseID', 'tagID']);
        if (requiredValidation) {
          return requiredValidation;
        }
    
        // Execute with standardized error handling
        return await this.executeWithErrorHandling(
          `Delete Tag: ${tagID} from Case: ${caseID}`,
          async () => await this.pegaClient.deleteCaseTag(caseID.trim(), tagID.trim()),
          { sessionInfo }
        );
      } catch (error) {
        return {
          content: [{
            type: 'text',
            text: `## Error: Delete Tag: ${tagID} from Case: ${caseID}\n\n**Unexpected Error**: ${error.message}\n\n${sessionInfo ? `**Session**: ${sessionInfo.sessionId} (${sessionInfo.authMode} mode)\n` : ''}*Error occurred at: ${new Date().toISOString()}*`
          }]
        };
      }
    }
  • Static method providing the tool definition for MCP protocol, including name 'delete_case_tag', description, and input schema requiring caseID and tagID.
    static getDefinition() {
      return {
        name: 'delete_case_tag', 
        description: 'Delete a specific tag from a case by case ID and tag ID',
        inputSchema: {
          type: 'object',
          properties: {
            caseID: {
              type: 'string',
              description: 'Case ID. Example: "MYORG-APP-WORK C-1001". Complete identifier including spaces."OSIEO3-DOCSAPP-WORK T-561003". a complete case identifier including spaces and special characters.'
            },
            tagID: {
              type: 'string',
              description: 'Tag ID to be deleted from the case. This is the unique identifier of the specific tag to remove.'
            },
            sessionCredentials: getSessionCredentialsSchema()
          },
          required: ['caseID', 'tagID']
        }
      };
    }
  • PegaClient wrapper for deleting a case tag, checks if 'tags' feature is available, then delegates to the underlying client implementation.
    async deleteCaseTag(caseID, tagID) {
      if (!this.isFeatureAvailable('tags')) {
        this.throwUnsupportedFeatureError('tags', 'deleteCaseTag');
      }
      return this.client.deleteCaseTag(caseID, tagID);
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. While it correctly indicates this is a destructive operation ('Delete'), it doesn't mention permission requirements, whether the deletion is permanent or reversible, error conditions, or what happens if the tag doesn't exist. For a mutation tool with zero annotation coverage, this is a significant gap.

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?

The description is a single, efficient sentence that gets straight to the point with zero wasted words. It's appropriately sized for a straightforward operation and front-loads the essential information.

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

Completeness2/5

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

For a destructive mutation tool with no annotations and no output schema, the description is insufficient. It doesn't explain what happens after deletion (success response, error handling), doesn't mention authentication requirements despite the complex sessionCredentials parameter, and provides no behavioral context about the deletion operation's consequences.

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 schema already documents all three parameters thoroughly. The description mentions 'case ID and tag ID' which aligns with the two required parameters, but adds no additional semantic context beyond what's already in the schema descriptions. This meets the baseline for high schema coverage.

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

Purpose4/5

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

The description clearly states the action ('Delete') and target ('a specific tag from a case'), making the purpose immediately understandable. However, it doesn't distinguish this tool from sibling tools like 'delete_case_tags' (plural) or other deletion tools, which would require explicit differentiation for a perfect score.

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?

The description provides no guidance on when to use this tool versus alternatives. There are multiple sibling deletion tools (delete_case, delete_case_follower, delete_attachment, etc.), but no indication of when this specific tag deletion is appropriate versus other deletion operations.

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/marco-looy/pega-dx-mcp'

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