Skip to main content
Glama
Sign In
Copilot Studio MCP

Copilot Studio MCP

by jgt87
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Pack workspace into a solution zip

cs_pack

Package a Copilot Studio agent workspace into a Dataverse solution .zip locally without sign-in, and run a quick structural check before export.

Instructions

pac copilot pack: local-only packaging of the workspace into a Dataverse solution .zip (no sign-in). Also a cheap structural check of the workspace. outputPath must be outside the workspace.

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": {
      "publisherPrefix": "<publisherPrefix>"
    },
    "name": "cs_pack"
  }
}

Input Schema

NameRequiredDescriptionDefault
workspaceNoPath to (or inside) the agent workspace. Defaults to CPS_WORKSPACE or the current directory.
outputPathNo
solutionNameNo
publisherPrefixYes

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

B3.4/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. It does disclose two valuable traits — no authentication is required and the operation is local-only — plus a hard constraint on outputPath. However, it says nothing about overwrite behavior, failure modes, or what the 'structural check' actually reports.

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?

Three compact sentences with the core purpose front-loaded and zero filler. The "pac copilot pack:" prefix is slightly redundant with the tool name, but otherwise the structure is tight.

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 4-parameter tool with no annotations, no output schema, and 25% schema coverage, the description covers purpose, auth profile, and one constraint, but leaves half the parameters and any return/failure behavior unexplained. Adequate but with visible gaps.

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 only 25% (workspace is the sole documented parameter), so the description must compensate. It adds a real constraint for outputPath ("must be outside the workspace"), but solutionName and publisherPrefix remain undocumented in both the schema and the description.

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+resource: packaging the workspace into a Dataverse solution .zip, plus a secondary role as a structural check. It is clear what the tool does, but it never distinguishes itself from the sibling cs_pack_solution, which an agent could easily confuse it with.

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?

"local-only ... (no sign-in)" and "cheap structural check" imply the context in which this is appropriate, but there is no explicit when-to-use versus cs_pack_solution or cs_check_solution, and no stated prerequisites. Usage is implied rather than directed.

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