Skip to main content
Glama
marco-looy

Pega DX MCP Server

by marco-looy

get_case_followers

Retrieve users following a Pega case to view notification recipients and track updates. Input a case ID to get follower details.

Instructions

Get the list of all the Case Followers. Retrieves information about users who are following a case to receive notifications and updates.

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.
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 implementing the get_case_followers tool logic: parameter validation, session initialization, and delegation to pegaClient.getCaseFollowers with error handling.
    async execute(params) {
      const { caseID } = params;
      let sessionInfo = null;
    
      try {
        sessionInfo = this.initializeSessionConfig(params);
    
        // Validate required parameters using base class
        const requiredValidation = this.validateRequiredParams(params, ['caseID']);
        if (requiredValidation) {
          return requiredValidation;
        }
    
        // Execute with standardized error handling
        return await this.executeWithErrorHandling(
          `Get Case Followers: ${caseID}`,
          async () => await this.pegaClient.getCaseFollowers(caseID.trim()),
          { sessionInfo }
        );
      } catch (error) {
        return {
          content: [{
            type: 'text',
            text: `## Error: Get Case Followers: ${caseID}\n\n**Unexpected Error**: ${error.message}\n\n${sessionInfo ? `**Session**: ${sessionInfo.sessionId} (${sessionInfo.authMode} mode)\n` : ''}*Error occurred at: ${new Date().toISOString()}*`
          }]
        };
      }
    }
  • Defines the MCP tool definition including name 'get_case_followers', description, and input schema requiring 'caseID' parameter.
    static getDefinition() {
      return {
        name: 'get_case_followers',
        description: 'Get the list of all the Case Followers. Retrieves information about users who are following a case to receive notifications and updates.',
        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.'
            },
            sessionCredentials: getSessionCredentialsSchema()
          },
          required: ['caseID']
        }
      };
    }
  • PegaClient router method for getCaseFollowers that enforces V2-only availability and delegates to the underlying version-specific client.
    async getCaseFollowers(caseID) {
      if (!this.isFeatureAvailable('followers')) {
        this.throwUnsupportedFeatureError('followers', 'getCaseFollowers');
      }
      return this.client.getCaseFollowers(caseID);
    }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states this is a retrieval operation ('Get', 'Retrieves information'), which implies read-only behavior, but doesn't specify authentication requirements, rate limits, pagination, error conditions, or what happens when no followers exist. For a tool with no annotation coverage, this leaves significant behavioral gaps.

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 appropriately concise with two clear sentences that state the purpose and what information is retrieved. It's front-loaded with the core functionality and avoids unnecessary elaboration. Every sentence earns its place, though it could be slightly more structured with usage context.

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 tool with no annotations, no output schema, and complex authentication parameters, the description is incomplete. It doesn't address what the tool returns (list format, user details), authentication requirements, error handling, or how it differs from related tools. The description alone is insufficient for an agent to fully understand the tool's behavior and usage context.

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 both parameters thoroughly. The description adds no parameter-specific information beyond what's in the schema - it doesn't explain the relationship between caseID and followers, or provide context about the sessionCredentials parameter. Baseline 3 is appropriate when schema does the heavy lifting.

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 tool's purpose: 'Get the list of all the Case Followers' and specifies it retrieves information about users following a case for notifications. It uses a specific verb ('Get') and resource ('Case Followers'), but doesn't explicitly differentiate from sibling tools like 'get_case_participants' or 'delete_case_follower'.

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. It doesn't mention sibling tools like 'get_case_participants' (which might overlap) or 'delete_case_follower' (which is the inverse operation). There's no context about prerequisites or typical use cases beyond the basic purpose.

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