Skip to main content
Glama
marco-looy

Pega DX MCP Server

by marco-looy

delete_case_follower

Remove a user from a case's follower list to stop case notifications and updates for that user.

Instructions

Remove a follower from a case, ending their subscription to case notifications and updates. Removes the follower association between case and user.

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.
followerIDYesUser ID of the follower to remove from the case. This is the unique identifier for the user in the Pega system who will no longer follow the case.
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 DeleteCaseFollowerTool class - the full tool implementation including the execute() method that handles the delete_case_follower logic. It extends BaseTool, validates required parameters (caseID, followerID), and calls pegaClient.deleteCaseFollower().
    import { BaseTool } from '../../registry/base-tool.js';
    import { getSessionCredentialsSchema } from '../../utils/tool-schema.js';
    
    export class DeleteCaseFollowerTool extends BaseTool {
      /**
       * Get the category this tool belongs to
       */
      static getCategory() {
        return 'followers';
      }
    
      /**
       * Get tool definition for MCP protocol
       */
      static getDefinition() {
        return {
          name: 'delete_case_follower',
          description: 'Remove a follower from a case, ending their subscription to case notifications and updates. Removes the follower association between case and user.',
          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.'
              },
              followerID: {
                type: 'string',
                description: 'User ID of the follower to remove from the case. This is the unique identifier for the user in the Pega system who will no longer follow the case.'
              },
              sessionCredentials: getSessionCredentialsSchema()
            },
            required: ['caseID', 'followerID']
          }
        };
      }
    
      /**
       * Execute the delete case follower operation
       */
      async execute(params) {
        const { caseID, followerID } = params;
        let sessionInfo = null;
    
        try {
          sessionInfo = this.initializeSessionConfig(params);
    
          // Validate required parameters using base class
          const requiredValidation = this.validateRequiredParams(params, ['caseID', 'followerID']);
          if (requiredValidation) {
            return requiredValidation;
          }
    
          // Execute with standardized error handling
          return await this.executeWithErrorHandling(
            `Delete Case Follower: ${caseID} - ${followerID}`,
            async () => await this.pegaClient.deleteCaseFollower(caseID.trim(), followerID.trim()),
            { sessionInfo }
          );
        } catch (error) {
          return {
            content: [{
              type: 'text',
              text: `## Error: Delete Case Follower: ${caseID} - ${followerID}\n\n**Unexpected Error**: ${error.message}\n\n${sessionInfo ? `**Session**: ${sessionInfo.sessionId} (${sessionInfo.authMode} mode)\n` : ''}*Error occurred at: ${new Date().toISOString()}*`
            }]
          };
        }
      }
    }
  • Tool definition with inputSchema for delete_case_follower, defining required parameters: caseID (string) and followerID (string), plus optional sessionCredentials.
    static getDefinition() {
      return {
        name: 'delete_case_follower',
        description: 'Remove a follower from a case, ending their subscription to case notifications and updates. Removes the follower association between case and user.',
        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.'
            },
            followerID: {
              type: 'string',
              description: 'User ID of the follower to remove from the case. This is the unique identifier for the user in the Pega system who will no longer follow the case.'
            },
            sessionCredentials: getSessionCredentialsSchema()
          },
          required: ['caseID', 'followerID']
        }
      };
    }
  • The tool is auto-discovered by ConfigurableToolLoader (src/registry/configurable-tool-loader.js) and ToolLoader (src/registry/tool-loader.js) by scanning the 'followers' category directory. The tool name 'delete_case_follower' is defined via getDefinition().name = 'delete_case_follower' at line 17.
    import { BaseTool } from '../../registry/base-tool.js';
    import { getSessionCredentialsSchema } from '../../utils/tool-schema.js';
    
    export class DeleteCaseFollowerTool extends BaseTool {
      /**
       * Get the category this tool belongs to
       */
      static getCategory() {
        return 'followers';
      }
    
      /**
       * Get tool definition for MCP protocol
       */
      static getDefinition() {
        return {
          name: 'delete_case_follower',
          description: 'Remove a follower from a case, ending their subscription to case notifications and updates. Removes the follower association between case and user.',
          inputSchema: {
            type: 'object',
            properties: {
              caseID: {
  • PegaClient.deleteCaseFollower() - the API client method that the tool calls. Checks if the 'followers' feature is available, then delegates to this.client.deleteCaseFollower().
    async deleteCaseFollower(caseID, followerID) {
      if (!this.isFeatureAvailable('followers')) {
        this.throwUnsupportedFeatureError('followers', 'deleteCaseFollower');
      }
      return this.client.deleteCaseFollower(caseID, followerID);
    }
Behavior3/5

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

No annotations are provided, so the description must carry the full burden. It states that the tool removes the follower association and ends their subscription. However, it does not disclose side effects (e.g., whether the user is notified, if the action is reversible, or required permissions).

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 concise with two sentences. The first sentence front-loads the action and primary effect. The second sentence slightly rephrases but adds minimal new information. No wasted words.

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

Completeness4/5

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

Given the simple nature of this write operation and the absence of an output schema, the description adequately covers the tool's purpose and immediate effect. It does not address error conditions or prerequisites, but for a straightforward removal action, it is sufficiently complete.

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?

The input schema has 100% coverage with detailed descriptions for caseID, followerID, and sessionCredentials. The description adds no additional meaning beyond what the schema already provides, so the baseline score of 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 uses the clear verb 'remove' and specifies the resource 'follower from a case'. It explicitly states the effect of ending notifications and removing the association, which distinguishes it from sibling tools like 'add_case_followers' and 'get_case_followers'.

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

Usage Guidelines3/5

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

The description does not explicitly state when to use this tool versus alternatives (e.g., delete_participant for other roles). However, the purpose is clear enough that an agent can infer it is for removing followers specifically, not other case participants.

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