Skip to main content
Glama
Sign In
Copilot Studio MCP

Copilot Studio MCP

by jgt87
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Snapshot an environment

cs_snapshot_environment

Capture a Copilot Studio environment into a folder for version comparison or history, including agents, flows, connection references, variables, and publish state. Read-only.

Instructions

Capture one environment into a folder for comparison or history: solution version, every agent cloned with pac copilot clone (agents/), and, when signed in, flows, connection references, environment variables and publish state. Read-only for the environment.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "label": "<label>",
      "environment": "<environment>",
      "dir": "<dir>"
    },
    "name": "cs_snapshot_environment"
  }
}

Input Schema

NameRequiredDescriptionDefault
dirYesSnapshot folder (recreated)
labelYesShort name such as DEV, TEST, ACC, PROD
agentsNoAgent schema names or ids to clone; default: every agent pac copilot list returns
clientIdNoEntra app (client) id for MSAL. Defaults to CPS_CLIENT_ID, then the first-party VS Code id.
solutionNoSolution unique name to record version/managed state for
tenantIdNoEntra tenant id. Defaults to the workspace sync metadata, then CPS_TENANT_ID.
maxAgentsNoDefault 20
environmentYesEnvironment id or URL
includeDataverseNoDefault true: flows, connection references, environment variables and publish state via Dataverse (needs cs_login; skipped silently otherwise)

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.8/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses that the environment is read-only, that agents are cloned with pac copilot clone into agents/<name>, and that Dataverse-sourced items are included only when signed in and are skipped silently otherwise. These are meaningful behavioral details, though it could further explain failure modes or permissions.

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?

The description is compact and front-loaded: it begins with the core action, then lists captured artifacts, then closes with the read-only guarantee. Every sentence contributes useful information, and there is no redundant restatement of the title or schema.

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?

Given nine parameters, no output schema, and no annotations, the description provides enough context to understand what the tool captures and its read-only nature. It even indicates the folder layout for agents (agents/<name>). It stops short of describing the returned snapshot structure or how comparison/history should consume the folder, but the essentials are present.

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 the input schema already documents all nine parameters, including agent selection, solution name, and includeDataverse behavior. The description adds some context about what gets captured and the signed-in condition for Dataverse items, but it does not significantly extend parameter meaning beyond the schema. A baseline 3 is appropriate.

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 verb and resource: capture one environment into a folder for comparison or history. It also enumerates what gets captured: solution version, agents, flows, connection references, environment variables, and publish state. It does not explicitly distinguish itself from sibling comparison tools such as cs_compare_snapshots or cs_compare_environments, so it falls short of a 5.

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 phrase 'for comparison or history' implies the intended use case, and 'Read-only for the environment' clarifies the operation's nature. However, the description does not explicitly say when to use this tool versus alternatives like cs_compare_snapshots, cs_compare_environments, or cs_check_drift. Usage guidance is therefore only implied.

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