Skip to main content
Glama
marco-looy

Pega DX MCP Server

by marco-looy

get_case_participants

Retrieve all participants for a specific Pega case to manage access and collaboration. Provides roles, permissions, and contact details for case oversight.

Instructions

Get all participants associated with a specific Pega case. Returns comprehensive list of case participants with their roles, permissions, and contact information for case access management.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
caseIDYesCase ID. Example: "MYORG-APP-WORK C-1001". Complete identifier including spaces."ON6E5R-DIYRecipe-Work-RecipeCollection R-1008". 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 main handler function that destructures the caseID from params, initializes session config, validates required parameters, executes the pegaClient.getCaseParticipants call within standardized error handling, and returns formatted error response if exception occurs.
    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(
          `Case Participants: ${caseID}`,
          async () => await this.pegaClient.getCaseParticipants(caseID.trim()),
          { caseID: caseID.trim(), sessionInfo }
        );
      } catch (error) {
        return {
          content: [{
            type: 'text',
            text: `## Error: Case Participants: ${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 MCP tool definition including the tool name 'get_case_participants', detailed description, and input schema specifying the required 'caseID' string parameter along with optional session credentials.
    static getDefinition() {
      return {
        name: 'get_case_participants',
        description: 'Get all participants associated with a specific Pega case. Returns comprehensive list of case participants with their roles, permissions, and contact information for case access management.',
        inputSchema: {
          type: 'object',
          properties: {
            caseID: {
              type: 'string',
              description: 'Case ID. Example: "MYORG-APP-WORK C-1001". Complete identifier including spaces."ON6E5R-DIYRecipe-Work-RecipeCollection R-1008". a complete case identifier including spaces and special characters.'
            },
            sessionCredentials: getSessionCredentialsSchema()
          },
          required: ['caseID']
        }
      };
  • Helper method in PegaClient router that checks if 'participants' feature is available in the current API version (V2 only), throws appropriate error if not, and delegates the getCaseParticipants call to the underlying V1/V2 client implementation.
    async getCaseParticipants(caseID) {
      if (!this.isFeatureAvailable('participants')) {
        this.throwUnsupportedFeatureError('participants', 'getCaseParticipants');
      }
      return this.client.getCaseParticipants(caseID);
    }
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states the tool 'Returns comprehensive list' but lacks details on pagination, rate limits, authentication requirements (implied by sessionCredentials parameter but not described), or error handling. For a read operation with no annotation coverage, this is insufficient behavioral disclosure.

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 a single, well-structured sentence that efficiently conveys the tool's purpose and return value. It's front-loaded with the core action and avoids unnecessary elaboration, though it could be slightly more concise by removing 'for case access management' which is somewhat redundant.

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 read tool with 2 parameters (1 required), 100% schema coverage, and no output schema, the description is minimally adequate. It explains what the tool does but lacks details on authentication behavior, response format, or error cases. With no annotations and no output schema, it should provide more behavioral context to be fully 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?

Schema description coverage is 100%, so the schema fully documents both parameters. The description adds no parameter-specific information beyond what's in the schema (e.g., it doesn't clarify caseID format or sessionCredentials usage). Baseline 3 is appropriate when the schema does all the parameter documentation work.

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 verb 'Get' and the resource 'participants associated with a specific Pega case', specifying it returns a comprehensive list with roles, permissions, and contact information. This distinguishes it from sibling tools like 'get_participant' (singular) and 'get_case' (general case info).

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 like 'get_participant' (singular participant) or 'get_case' (case details without participants). It mentions 'case access management' as a context but gives no explicit when/when-not instructions or prerequisites.

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