Skip to main content
Glama
marco-looy

Pega DX MCP Server

by marco-looy
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
JavaScript
Hybrid

delete_data_record

Deletes a data record by supplying the savable Data Page ID and primary key parameters. Uses conditional save plan for deletion, supported on data object classes.

Instructions

Delete a data record based on conditional save plan configured for a savable Data Page. Only supported on data object classes. Requires primary key(s) to uniquely identify the record to delete.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataViewIDYesID of savable Data Page containing the record to delete. a valid data page identifier configured for delete operations.
dataViewParametersYesPrimary key(s) as JSON string to uniquely identify the data record to delete. a valid JSON object containing key-value pairs. For example: "{\"CustomerID\": \"12345\"}" or "{\"OrderID\": \"O-1001\", \"CustomerID\": \"C-5678\"}". Note: String format like "CustomerID=12345" will cause validation errors.
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.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed3 schema fields changedv1.0.0
    • changedInput schema / properties / dataViewID / description
      Previous value: -"ID of savable Data Page containing the record to delete. Must be a valid data page identifier configured for delete operations."New value: +"ID of savable Data Page containing the record to delete. a valid data page identifier configured for delete operations."
    • changedInput schema / properties / dataViewParameters / description
      Previous value: -"Primary key(s) as input to uniquely identify the data record to delete. The exact format depends on the data page configuration and may include multiple key-value pairs. For example: \"CustomerID=12345\" or \"OrderID=O-1001&CustomerID=C-5678\"."New value: +"Primary key(s) as JSON string to uniquely identify the data record to delete. a valid JSON object containing key-value pairs. For example: \"{\\\"CustomerID\\\": \\\"12345\\\"}\" or \"{\\\"OrderID\\\": \\\"O-1001\\\", \\\"CustomerID\\\": \\\"C-5678\\\"}\". Note: String format like \"CustomerID=12345\" will cause validation errors."
    • addedInput schema / properties / sessionCredentials
      Added value: +{
+  "description": "Optional 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.",
+  "properties": {
+    "accessToken": {
+      "description": "Direct access token (required for token mode)",
+      "type": "string"
+    },
+    "apiVersion": {
+      "default": "v2",
+      "description": "API version (optional, defaults to v2)",
+      "type": "string"
+    },
+    "baseUrl": {
+      "description": "Pega base URL (required if providing credentials)",
+      "type": "string"
+    },
+    "clientId": {
+      "description": "OAuth2 client ID (required for OAuth mode)",
+      "type": "string"
+    },
+    "clientSecret": {
+      "description": "OAuth2 client secret (required for OAuth mode)",
+      "type": "string"
+    },
+    "sessionId": {
+      "description": "Optional session ID. If not provided, a new session will be created.",
+      "type": "string"
+    },
+    "tokenExpiry": {
+      "description": "Token expiry in seconds from now (optional for token mode)",
+      "type": "number"
+    }
+  },
+  "type": "object"
+}
  2. First observed

TDQS

B3.1/5.0
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 'Delete' (destructive) but does not explain side effects, authorization requirements, rate limits, or implications of the 'conditional save plan'. This is insufficient for a destructive operation.

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 two sentences, concise and front-loaded with the primary action. However, it could be slightly more structured to separate purpose from requirements. Overall, no waste.

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?

Given the lack of annotations and output schema, the description does not provide enough context about behavior (e.g., what happens on success/failure, handling of conditional save plan, or interaction with credentials). A delete operation with nested parameters needs more 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 coverage is 100%, and the schema already provides detailed descriptions for all parameters, including examples for dataViewParameters. The description adds 'Requires primary key(s)' which aligns with schema but does not add significant new meaning beyond structured data.

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 'Delete a data record' and specifies it is for savable Data Pages and data object classes, distinguishing it from other deletion tools like delete_case or delete_attachment. However, it could more explicitly differentiate from sibling tools like update_data_record_full.

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 mentions prerequisites (conditional save plan, primary keys) but does not provide guidance on when to use this tool versus alternatives (e.g., when to delete vs. update) or when not to use it. The context is implied but not explicit.

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