Skip to main content
Glama

db_sync

DestructiveIdempotent

Dry-run or execute a preflight-checked Dataverse database synchronization from Visual Studio, requiring confirmed target or environment and policy approval for real runs.

Instructions

Dry-run or run a full database synchronization through Visual Studio. Always runs preflight checks. A local runtime syncs only databaseSync.target (confirmDatabase must equal its database name). A CloudRuntime environment syncs only databaseSync.finOpsUri, which must be the environment Visual Studio is connected to (confirmEnvironment must equal its host); it needs databaseSync.allowCloudRuntime and a connection confirmed this session, and never opens a connection wizard. A real run also needs policies.allowDatabaseSynchronization and dryRun=false. The online sync reports no result of its own, so the extension watches the Power Platform output for the Dataverse async operation status (30 succeeded, 31 failed, 32 canceled); success is null if none appears before timeoutMs.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "db_sync"
  }
}

Input Schema

NameRequiredDescriptionDefault
dryRunNo
timeoutMsNo
confirmDatabaseNo
confirmEnvironmentNo

Output Schema

NameRequiredDescriptionDefault
okYes
modeNo
errorNo
readyNo
checksNo
dryRunNo
outputNo
targetNo
logsUrlNo
successNo
auditLogNo
completionNo
durationMsNo
errorCountNo
logArchiveNo
environmentNo
warningCountNo
outputTruncatedNo
runtimeHostTypeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.16.0

TDQS

A4.6/5.0
Behavior5/5

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

Despite annotations already flagging destructive/write behavior, the description adds substantial context: preflight checks always run, no connection wizard is opened, the online sync emits no own result and success is inferred from Power Platform output codes 30/31/32, and success is null on timeout. That is exactly the behavior an agent needs before invoking 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?

Front-loaded with the core action and dry-run default, and nearly every clause carries required constraint data. However, it is one dense paragraph with heavy dotted-path references that would read better as a bulleted list of runtime prerequisites.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive, externally observable mutation tool this covers the essentials — safety prerequisites, runtime branching, and the unusual result-reporting mechanism (output-watching with status codes). Since an output schema exists, the description is not obliged to detail return values, and the null-on-timeout caveat fills the one gap that matters.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% with no descriptions, so the description must carry the parameters — and it explains all four: dryRun=false for a real run, timeoutMs as the output-watch window, and confirmDatabase/confirmEnvironment as confirmation guards matched against target/host. It omits units and bounds on timeoutMs, so not fully complete.

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?

States a specific verb and resource ('dry-run or run a full database synchronization through Visual Studio') plus scope (daily preflight checks, local vs CloudRuntime). An agent can immediately tell this is the sync-execution tool rather than the connection or environment tools in the sibling list.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives concrete conditions that gate the call: local runtime requires confirmDatabase equal to databaseSync.target, CloudRuntime requires confirmEnvironment equal to the connected host plus allowCloudRuntime and a connection confirmed this session, and a real run requires policies.allowDatabaseSynchronization and dryRun=false. It never names an alternative tool to use instead, so it falls short of the explicit when-not/alternatives bar.

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