Skip to main content
Glama
Sign In
Copilot Studio MCP

Copilot Studio MCP

by jgt87
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Sync a solution project from the environment

cs_sync_solution

Re-exports a solution and updates an existing unpacked folder or .cdsproj to match the environment's current state, running pac solution sync without modifying the environment.

Instructions

Re-export the solution and update an existing unpacked solution folder or .cdsproj with the environment's current state. Read-only for the environment. Runs 'pac solution sync' with the active pac auth profile.

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": "cs_sync_solution"
  }
}

Input Schema

NameRequiredDescriptionDefault
cwdNoWorking directory for pac (for project commands: the solution project folder)
mapNoMapping XML file for component folders
asyncNoRun the operation asynchronously
includeNoSettings to include in the export (pac solution export --include values)
profileNopac auth profile to run as: the admin account for tenant commands. Defaults to CPS_ADMIN_PROFILE for admin commands and CPS_PAC_PROFILE otherwise, then the active profile. cs_init lists the profiles.
localizeNoExtract string resources into .resx files
backgroundNoRun in the background and return a jobId immediately, for a command that takes longer than the client will wait. Poll cs_job_status.
environmentNoEnvironment id or URL; default: the environment of the active pac auth profile
packageTypeNoUnmanaged, Managed or Both (default Both)
solutionFolderNoUnpacked solution folder (Other/Solution.xml root) or .cdsproj folder; default: cwd
timeoutSecondsNoDefault 3600
maxAsyncWaitTimeNoMax asynchronous wait time in minutes (default 60)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.8
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observedv0.1.5

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations the description carries the full burden, and it does add real context: the operation is 'read-only for the environment' and runs 'pac solution sync' with the active auth profile. The critical gap is the local side — it does not say whether local unpacked files are overwritten or whether local edits are lost, nor what the sync returns.

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?

Two sentences, zero filler, and the core action (re-export and update the local project) is front-loaded before the safety note and implementation detail. Every clause earns its place.

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?

For a 12-parameter, zero-required, annotation-free mutation-of-local-files tool with no output schema, the description is adequate but thin. It covers direction and the environment-side safety property but omits the local overwrite semantics and result shape that an agent would need to call it responsibly.

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 all 12 parameters are already documented in the schema, including profile defaults, solutionFolder, environment and packageType. The description adds essentially nothing beyond the parameter layer except that it uses the active pac auth profile. Baseline 3 is appropriate when the schema does the heavy lifting.

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?

States a specific verb and resource: re-export the solution and update an existing unpacked folder or .cdsproj, plus the underlying command ('pac solution sync'). The word 'existing' implicitly separates it from creation-style siblings like cs_init_solution_project or cs_clone_solution, though it never names cs_pull_solution/cs_import_solution as the contrasting alternatives.

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?

Usage is implied by scope ('update an EXISTING unpacked solution folder or .cdsproj'), which tells the agent it needs a solution project already on disk. However there is no explicit when-to-use/when-not statement and no sibling is named, so routing between this, cs_pull_solution, cs_check_solution and cs_pack_solution is left to inference.

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

Deploy Server

Other Tools