Skip to main content
Glama
Sign In
Copilot Studio MCP

Copilot Studio MCP

by jgt87
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Pack an unpacked solution folder

cs_pack_solution

Zip an unpacked solution source folder after local edits so it can be deployed. Provide folder, zip, and package type to create the deployment package.

Instructions

pac solution pack: zip an unpacked source folder (after local edits) so it can be deployed.

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": {
      "folder": "<folder>",
      "zip": "<zip>"
    },
    "name": "cs_pack_solution"
  }
}

Input Schema

NameRequiredDescriptionDefault
zipYes
folderYes
packagetypeNo

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

C2.9/5.0
Behavior2/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 conveys that the operation is a local zip creation, but never says whether the output zip is overwritten if it exists, whether the folder must be a valid unpacked solution, what errors arise on bad input, or what authorization/environment context is required.

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?

A single front-loaded sentence that maps directly to the CLI verb and wastes no words. It is efficient, though the brevity is partly the source of the documentation gaps elsewhere.

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

Completeness2/5

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

For a 3-parameter mutation tool with no annotations, no output schema, and 0% schema coverage, the description should cover packagetype semantics and the folder/zip contract. As written it leaves the agent guessing about a required enum that determines whether the packaged solution is managed or unmanaged.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 3 parameters, so the description must compensate. It loosely implies folder = source folder and zip = output archive, but says nothing about packagetype (Managed vs Unmanaged) even though that enum changes the artifact materially.

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: zipping an unpacked source folder into a deployable artifact, and even names the underlying command ('pac solution pack'). It does not however differentiate itself from the sibling cs_pack or explain the relationship to cs_pull / cs_push, so an agent must infer which pack-family tool applies.

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 parenthetical '(after local edits) so it can be deployed' implies the workflow position: run this after modifying an unpacked folder, before deployment. There are no explicit when-not conditions and no named alternatives (cs_pack, cs_push, cs_deploy_solution) to disambiguate a large pack/pull/push sibling set.

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