Skip to main content
Glama
jgt87

Copilot Studio MCP

by jgt87
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Create or update deployment settings

cs_create_deployment_settings

Creates deployment settings JSON that maps connection references and environment variables to target values for Copilot Studio solution deployment, listing any unmapped items.

Instructions

pac solution create-settings: the JSON that maps every connection reference (to a connection id in the target environment) and environment variable (to a target value). Pass connectionReferences / environmentVariables to fill values; the result lists what is still unmapped.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
zipNoSolution zip (or use solutionDir from cs_pull_solution)
regenerateNoRecreate the file even if it exists (mappings are lost)
solutionDirNoDirectory written by cs_pull_solution
settingsFileNoDefault <solutionDir>/deployment-settings.json or next to the zip
copilotAgentsNoagent schema name -> Entra security group id allowed to use the agent in the target
connectionReferencesNologicalName -> connectionId in the target environment
environmentVariablesNoschemaName -> value for the target

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.1.8
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / connectionReferences / propertyNames
      Added value: +{
+  "type": "string"
+}
    • addedInput schema / properties / copilotAgents / propertyNames
      Added value: +{
+  "type": "string"
+}
    • addedInput schema / properties / environmentVariables / propertyNames
      Added value: +{
+  "type": "string"
+}
  2. First observedv0.1.5

TDQS

B3.2/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 behavioral burden. It discloses that the result lists still-unmapped items, which is useful, but it does not explain file creation/overwrite behavior, that mappings can be lost on regeneration, permission requirements, or other side effects of writing deployment settings.

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 short and largely front-loaded around the pac command and the settings JSON concept. The phrasing is slightly telegraphic, but it avoids repetition and wasted text.

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?

The description covers the core purpose and mentions the result listing unmapped values, which partly compensates for the missing output schema. Still, for a seven-parameter nested-object tool with no annotations, it omits important context about file behavior, defaults, and how this step fits into deployment workflows.

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%, so the schema already documents all seven parameters, including nested objects and defaults. The description adds some meaning for connectionReferences and environmentVariables by explaining how they fill mappings, but it does not add semantic detail for the other parameters.

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 states a specific action tied to the pac solution create-settings command and identifies the resource: a deployment settings JSON mapping connection references and environment variables. It is clear enough to distinguish from most siblings, though it does not explicitly contrast with related deployment tools like cs_deploy_solution.

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 by saying to pass connectionReferences and environmentVariables to fill values, and that the result lists unmapped items. However, it does not state when to use this tool versus alternatives such as cs_pull_solution or cs_deploy_solution, nor does it give prerequisites or ordering guidance.

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