Skip to main content
Glama
Sign In
Copilot Studio MCP

Copilot Studio MCP

by jgt87
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Create a service-principal Dataverse connection

cs_create_connection

Create a Dataverse connection using an app registration (application ID and client secret) so pipeline-owned flows and tools run without a personal account. Requires confirm: true for live changes.

Instructions

Create a Dataverse connection that authenticates with an app registration (application id + client secret) so flows and tools owned by a pipeline do not depend on a person. This is the only connection kind pac can create; connector connections (SharePoint, Outlook, MCP servers ...) are still authorised in the portal. Runs 'pac connection create' with the active pac auth profile. Mutates a live environment: requires confirm: true (a dry run otherwise).

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": {
      "tenantId": "<tenantId>",
      "name": "<name>",
      "applicationId": "<applicationId>",
      "clientSecret": "<clientSecret>"
    },
    "name": "cs_create_connection"
  }
}

Input Schema

NameRequiredDescriptionDefault
cwdNoWorking directory for pac (for project commands: the solution project folder)
nameYesConnection display name
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.
tenantIdYesEntra tenant id
backgroundNoRun in the background and return a jobId immediately, for a command that takes longer than the client will wait. Poll cs_job_status.
environmentNoEnvironment id or URL; default: the environment of the active pac auth profile
clientSecretYesClient secret; prefer a secret from a vault, it is masked in logs (masked in logs and results)
applicationIdYesApp registration (client) id
timeoutSecondsNoDefault 600

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

A4.4/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the burden; it discloses the mutation of a live environment, the mandatory confirm: true gate with dry-run fallback, and that it wraps 'pac connection create' under the active auth profile. Missing only the return/dry-run payload shape, which holds it back from a 5.

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?

Four tight sentences, front-loaded with the purpose and immediately followed by the scope exclusion and the safety gate. No filler or redundancy.

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 10 parameters and no output schema, the description covers the critical decision points (mutation safety, confirm gate, portal-only alternative) and leaves scheduling/timeout details to the schema. A note on what a dry run returns would make it complete.

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 nearly all parameter meaning is already documented (confirm, profile, clientSecret masking, background, environment). The description adds only conceptual framing for applicationId/clientSecret rather than new per-parameter detail, so baseline 3 applies.

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?

Specific verb and resource (create a Dataverse connection) plus the exact auth mechanism (app registration application id + client secret) and the motivating rationale (don't depend on a person). It also explicitly distinguishes this from connector connections, which cannot be created this way.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

States plainly that this is the only connection kind pac can create and that connector connections (SharePoint, Outlook, MCP servers) must be authorised in the portal instead — an explicit when-not and alternative. It also names the dry-run-by-default condition that governs invocation.

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