Skip to main content
Glama
marco-looy

Pega DX MCP Server

by marco-looy

get_data_objects

Retrieve available data objects with metadata and links from Pega DX MCP Server. Filter by data or case types to find specific objects for integration.

Instructions

Retrieve list of available data objects with metadata and HATEOAS links. Can optionally filter by data object type (data or case).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNoFilter for data object type. Returns "data" or "case" type objects.
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 implements the core handler logic for the 'get_data_objects' tool. It handles input parameters (type), session initialization, enum validation, error handling, and calls the underlying pegaClient.getDataObjects({ type }).
    async execute(params) {
      const { type } = params;
      let sessionInfo = null;
    
      try {
        sessionInfo = this.initializeSessionConfig(params);
    
        // Validate enum parameters if provided
        const enumValidation = this.validateEnumParams(params, {
          type: ['data', 'case']
        });
        if (enumValidation) {
          return enumValidation;
        }
    
        // Execute with standardized error handling
        return await this.executeWithErrorHandling(
          `Data Objects List${type ? ` (type: ${type})` : ''}`,
          async () => await this.pegaClient.getDataObjects({ type }),
          { sessionInfo }
        );
      } catch (error) {
        return {
          content: [{
            type: 'text',
            text: `## Error: Data Objects List${type ? ` (type: ${type})` : ''}\n\n**Unexpected Error**: ${error.message}\n\n${sessionInfo ? `**Session**: ${sessionInfo.sessionId} (${sessionInfo.authMode} mode)\n` : ''}*Error occurred at: ${new Date().toISOString()}*`
          }]
        };
      }
    }
  • Static getDefinition() provides the tool schema including name 'get_data_objects', description, and inputSchema with optional 'type' (enum: 'data', 'case') and sessionCredentials.
    static getDefinition() {
      return {
        name: 'get_data_objects',
        description: 'Retrieve list of available data objects with metadata and HATEOAS links. Can optionally filter by data object type (data or case).',
        inputSchema: {
          type: 'object',
          properties: {
            type: {
              type: 'string',
              enum: ['data', 'case'],
              description: 'Filter for data object type. Returns "data" or "case" type objects.'
            },
            sessionCredentials: getSessionCredentialsSchema()
          },
          required: []
        }
      };
    }
  • Helper method in PegaClient class that wraps the underlying client.getDataObjects(options), directly invoked by the tool handler.
    async getDataObjects(options = {}) {
      return this.client.getDataObjects(options);
  • Dynamic registration logic in ToolLoader.loadToolFile where tools are discovered, validated, instantiated, and registered in loadedTools Map by their getDefinition().name. This is how get_data_objects is automatically registered during discovery.
    const toolInstance = new ToolClass();
    const toolName = ToolClass.getDefinition().name;
    
    this.loadedTools.set(toolName, {
      instance: toolInstance,
      class: ToolClass,
      category: category,
      filename: filename
    });
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 mentions the tool retrieves a list with metadata and HATEOAS links, which is useful. However, it doesn't describe important behavioral traits like whether this is a read-only operation (implied but not stated), potential rate limits, authentication requirements beyond the parameter schema, pagination behavior, or error handling. For a tool with complex authentication parameters and no annotations, 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is appropriately concise with two sentences that directly state the tool's purpose and optional filtering capability. It's front-loaded with the main functionality and avoids unnecessary elaboration. However, the second sentence could be slightly more integrated with the first for better flow.

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 moderate complexity (2 parameters with 100% schema coverage, no output schema, and no annotations), the description is minimally adequate. It covers the basic purpose and filtering option but lacks behavioral context needed for a tool with authentication parameters and no output schema. The description doesn't compensate for the absence of annotations or output schema details.

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 fully documents both parameters. The description adds minimal value by mentioning the optional filter by type ('data' or 'case'), which is already covered in the schema's enum description. It doesn't provide additional context about parameter interactions or usage beyond what's in the structured schema.

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: 'Retrieve list of available data objects with metadata and HATEOAS links.' It specifies the verb ('retrieve'), resource ('data objects'), and scope ('list with metadata and HATEOAS links'). However, it doesn't explicitly differentiate from sibling tools like 'get_cases' or 'get_data_view_metadata' beyond mentioning the optional type filter.

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 provides some usage context by mentioning the optional filter by data object type ('data' or 'case'), which implies when to use this tool for filtered retrieval. However, it doesn't explicitly state when to use this tool versus alternatives like 'get_cases' or 'get_data_view_metadata', nor does it provide exclusions or prerequisites for usage.

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