Pega DX MCP Server

update_data_record_full

Fully update an existing data record using a conditional save plan, replacing the entire record with a provided data object.

Instructions

Fully update an existing data record based on conditional save plan configured for a savable Data Page. Overrides the entire data record with the provided data object.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "dataViewID": "<dataViewID>",
      "data": "<data>"
    },
    "name": "update_data_record_full"
  }
}

Input Schema

Name	Required	Description
`data`	Yes	Data object containing all properties to update in the data record. This will replace the entire existing record.
`dataViewID`	Yes	ID of savable Data Page to update. a valid, existing data view identifier.
`sessionCredentials`	No	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.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv1.0.0Jan 3, 2026

changedInput schema / properties / dataViewID / description

Previous value: -"ID of savable Data Page to update. Must be a valid, existing data view identifier."New value: +"ID of savable Data Page to update. a valid, existing data view identifier."

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"
+}

First observedAug 15, 2025

TDQS

A3.5/5.0

Behavior2/5

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

With no annotations, the description carries the full burden. It mentions overriding the entire record but does not disclose behavioral traits such as authentication requirements, destructive nature, error handling, or what happens if the record does not exist. The reference to a conditional save plan adds context but is insufficient for full transparency.

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 concise, consisting of two sentences that front-load the core action and the data object role. Every word is meaningful, and the structure is efficient.

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 has no output schema and no annotations, the description covers the main action but lacks details on return values, error conditions, or additional behavioral context. The mention of a conditional save plan introduces a concept that is not explained further, leaving some gaps for a comprehensive understanding.

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?

The input schema covers all three parameters with clear descriptions. The 'data' parameter description notes that it replaces the entire record, aligning with the tool's purpose. Since schema coverage is 100%, the baseline is met, but the description adds minimal extra meaning beyond the schema.

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 tool performs a full update of an existing data record, overriding the entire record with a provided data object. It distinguishes from the sibling tool 'update_data_record_partial' by emphasizing the full replacement nature.

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 implies usage for full updates but does not explicitly state when to use this tool versus the partial update sibling. No prerequisites or context for the conditional save plan are provided, leaving the agent to infer usage from the name and description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server