Skip to main content
Glama
jgt87

Copilot Studio MCP

by jgt87
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Create an environment

cs_admin_create_environment

Create a Dataverse environment in your tenant as Production, Sandbox, Trial, Developer, or Teams. Requires confirmation to run; without confirm it performs a dry run.

Instructions

Create a Dataverse environment in the tenant. Consumes tenant capacity: requires confirm: true. Runs 'pac admin create' with the active pac auth profile. Mutates a live environment: requires confirm: true (a dry run otherwise).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cwdNoWorking directory for pac (for project commands: the solution project folder)
nameNoEnvironment name
typeYesProduction, Sandbox, Trial, Developer or Teams
userNoUser to assign to the environment (object id or UPN)
asyncNoRun the operation asynchronously
domainNoDomain part of the environment URL
regionNoRegion (default unitedstates)
confirmNoRequired to actually perform a change in a live environment. Without it the tool returns a dry run.
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.
currencyNoCurrency (default USD)
languageNoLanguage (default English)
inputFileNoJSON file with the arguments
templatesNoDynamics 365 templates to deploy
backgroundNoRun in the background and return a jobId immediately, for a command that takes longer than the client will wait. Poll cs_job_status.
timeoutSecondsNoDefault 7200
securityGroupIdNoEntra security group id (required for a Teams environment)
maxAsyncWaitTimeNoMax asynchronous wait time in minutes (default 60)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.5

TDQS

A4.3/5.0
Behavior5/5

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

With no annotations provided, the description carries the full transparency burden. It discloses tenant capacity consumption, that the tool mutates a live environment, the dry-run behavior without confirm, and reliance on the active pac auth profile. This is strong behavioral disclosure beyond the schema.

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 front-loaded with the core purpose. The only structural weakness is the duplicated 'requires confirm: true' clause appearing in both sentences, which makes it slightly less crisp than it could be.

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

Completeness4/5

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

For a high-complexity mutation tool with no annotations and no output schema, the description covers the essential operational context: side effects, safety switch, dry-run mode, and auth profile. Return shape is not described, but that is an acceptable gap given the detailed input schema and clear behavioral warnings.

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% for 17 parameters, so the baseline is 3. The description adds useful context about capacity consumption and the underlying pac admin create command, plus the profile behavior, but the confirm requirement is already accurately described in the schema. It does not substantially deepen semantics for most parameters.

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 states a specific verb and resource: 'Create a Dataverse environment in the tenant.' It also names the underlying command ('pac admin create'), which clearly distinguishes it from the admin delete, reset, copy, and restore sibling tools.

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?

The creation context is clear and the description provides a critical usage prerequisite: confirm: true is required to actually mutate a live environment, otherwise it is a dry run. It does not explicitly name alternatives or exclusionary conditions, but the purpose is unambiguous enough for an agent to select it correctly.

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