Skip to main content
Glama
jgt87

Copilot Studio MCP

by jgt87
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

How to use this server

cs_guide

Explains how to complete one part of Copilot Studio agent development, names the tools and order needed, and returns next steps for your workspace.

Instructions

Explain how to do one part of Copilot Studio agent development with this server's tools: 'getting-started' (clone or create an agent and take it to a published, tested state), 'instructions' (write the agent's instructions, with AI Builder or by hand), 'knowledge' (add public site, SharePoint, Graph connector or file knowledge), 'tools' (find a connector operation, add the tool, bind its connection), 'topics' (deterministic conversations: triggers and the node types), 'flows' (build a cloud flow, bind its connections, run it, and work out why a run failed), 'evaluations' (test sets, runs and results, plus local conversation tests), 'publish-and-test' (publish the agent and chat with it), 'drift' (changes made in the portal since the last sync, and how to merge them), 'transcripts' (what real users asked, how those sessions ended, and turning the failures into a test set), 'solutions' (pull a solution, redeploy it elsewhere, compare environments), 'administration' (tenant administration with a separate admin account, and backing the tenant configuration up to files), 'troubleshooting' (the errors this server can return, and what each one means). Read the relevant topic when you do not know which tools a job needs or what order they go in; it names the tool for each step and the manual portal steps that cannot be automated. It only explains - it changes nothing and does no work, so when the user asked for something to be built, written or run, call the tool that does it rather than this one. Also returns next steps for the workspace at hand.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
topicNoDefault getting-started
workspaceNoPath to (or inside) the agent workspace. Defaults to CPS_WORKSPACE or the current directory.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.6
    • changedInput schema / properties / topic / enum
      Previous value: -[
-  "getting-started",
-  "instructions",
-  "knowledge",
-  "tools",
-  "topics",
-  "evaluations",
-  "publish-and-test",
-  "drift",
-  "transcripts",
-  "solutions",
-  "administration",
-  "troubleshooting"
-]New value: +[
+  "getting-started",
+  "instructions",
+  "knowledge",
+  "tools",
+  "topics",
+  "flows",
+  "evaluations",
+  "publish-and-test",
+  "drift",
+  "transcripts",
+  "solutions",
+  "administration",
+  "troubleshooting"
+]
  2. First observedv0.1.5

TDQS

A4.6/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and largely meets it: it declares the tool is read-only and side-effect free ('it changes nothing and does no work') and discloses a return value ('next steps for the workspace at hand'). It does not discuss auth/setup prerequisites, but for a pure documentation tool the safety profile is adequately disclosed.

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?

Front-loaded with purpose and usage before the topic catalogue, and every topic gloss earns its place by mapping to a distinct job. The main weakness is that the thirteen glosses are packed into a single run-on sentence, which hurts scannability, though little could be cut without losing routing value.

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

Completeness5/5

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

No output schema exists, and the description compensates by stating what comes back ('next steps for the workspace at hand'). Combined with the exhaustive topic catalogue, the read-only guarantee, and the routing guidance, an agent has everything needed to decide whether and how to call it.

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

Parameters4/5

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

Schema coverage is 100%, so a 3 is the baseline, but the description goes beyond the bare enum by explaining what each topic value actually contains (e.g. 'topics' = triggers and node types, 'drift' = portal changes since last sync and how to merge them). The workspace parameter adds no description-level meaning, but the topic semantics are materially enriched.

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?

States a specific verb and resource ('Explain how to do one part of Copilot Studio agent development with this server's tools') and enumerates the exact scope via thirteen named topics. It explicitly contrasts itself with the action siblings: 'It only explains - it changes nothing and does no work.' An agent can distinguish it from cs_create_agent, cs_run_flow, etc. without opening any schema.

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?

Gives both the when-to-use condition ('Read the relevant topic when you do not know which tools a job needs or what order they go in') and the when-not condition ('when the user asked for something to be built, written or run, call the tool that does it rather than this one'). It also names what it returns for each step (the tool per step, plus manual portal steps that cannot be automated).

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