Skip to main content
Glama
marco-looy

Pega DX MCP Server

by marco-looy

delete_case_follower

Remove a user from following a case to stop their notifications and updates about that case.

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 execute method of DeleteCaseFollowerTool class that implements the tool's core logic: validates parameters, initializes session, and calls pegaClient.deleteCaseFollower with error handling.
    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()}*`
          }]
        };
      }
    }
  • Static getDefinition method providing the tool name, description, and input schema validation for the delete_case_follower tool.
      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']
        }
      };
    }
  • PegaClient method that checks if the followers feature is available and delegates the deleteCaseFollower call to the underlying SDK client.
    async deleteCaseFollower(caseID, followerID) {
      if (!this.isFeatureAvailable('followers')) {
        this.throwUnsupportedFeatureError('followers', 'deleteCaseFollower');
      }
      return this.client.deleteCaseFollower(caseID, followerID);
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It describes the action ('Remove a follower') and effect ('ending their subscription'), but lacks details on permissions required, whether the action is reversible, error handling, or rate limits. For a mutation tool with zero annotation coverage, this is a significant gap in behavioral context.

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 two concise sentences with zero waste, front-loaded with the core action and followed by clarifying details. Every word earns its place by explaining the tool's purpose and effect efficiently.

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?

Given the tool's complexity (mutation with 3 parameters, no output schema, and no annotations), the description is adequate but incomplete. It covers the what and why but lacks behavioral details like side effects, error cases, or response format. For a deletion tool, more context on permissions or consequences would improve completeness.

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 parameters thoroughly. The description does not add any parameter-specific information beyond what the schema provides, such as formatting hints or examples for 'caseID' or 'followerID'. Baseline 3 is appropriate when the schema does the heavy lifting.

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 specific action ('Remove a follower from a case') and the resource ('case notifications and updates', 'follower association between case and user'). It distinguishes from sibling tools like 'add_case_followers' by specifying removal rather than addition, and from 'delete_case' by targeting followers rather than the entire case.

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

Usage Guidelines4/5

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

The description implies usage context by stating it 'ends their subscription to case notifications and updates', suggesting it should be used when a user no longer needs updates. However, it does not explicitly state when to use this tool versus alternatives like 'delete_participant' or provide exclusions, though the purpose is clear enough to infer appropriate scenarios.

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