@loopops/mcp-server 3.7.0 → 3.8.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/tools/sfdc-sync.js +12 -1
- package/package.json +1 -1
package/dist/tools/sfdc-sync.js
CHANGED
|
@@ -42,9 +42,20 @@ export function registerSfdcSyncTools(server, allowed) {
|
|
|
42
42
|
"config/account_master/sfdc_deploy.yaml has initial_deployment.mode=review). Promotes the",
|
|
43
43
|
"account to pending_update_deployment so the next deploy run pushes it to SF.",
|
|
44
44
|
"",
|
|
45
|
+
"Always include a `reason` — it lands on the lifecycle event payload alongside a snapshot",
|
|
46
|
+
"of the account's score + key fields at approval time. Future operators can reconstruct",
|
|
47
|
+
"'why did we approve this back in May?' from the event row alone.",
|
|
48
|
+
"",
|
|
45
49
|
"Use this for the first push of every new account until you flip mode=auto in the YAML",
|
|
46
50
|
"(once you trust the eligibility filter + field map).",
|
|
47
|
-
].join("\n"),
|
|
51
|
+
].join("\n"), {
|
|
52
|
+
...accountIdentifierShape,
|
|
53
|
+
reason: z
|
|
54
|
+
.string()
|
|
55
|
+
.min(3)
|
|
56
|
+
.max(500)
|
|
57
|
+
.describe("Why this account is being approved (e.g. 'Tier-1 strategic prospect', 'Existing customer expansion target', 'Q3 ABM list'). Stored in the lifecycle event payload for audit."),
|
|
58
|
+
}, safeTool(async (input) => trpcMutation("mcp.approveInitialDeployment", input)));
|
|
48
59
|
}
|
|
49
60
|
if (allowed.has("deployment_status")) {
|
|
50
61
|
server.tool("deployment_status", "Top-line counts of accounts in each deployment lifecycle state (pending review, pending update, deployed, deployment_failed, sync_drift). Includes a sample of the initial-review queue so ops can spot-check what's waiting for approval.", {
|