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 Copilot Studio agent-development task: which server tools and manual portal steps to use, in what order, plus workspace next steps.

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

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.8
    • removedInput schema / additionalProperties
      Removed value: -false
  2. 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"
+]
  3. 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 behavioral burden. It discloses that the tool only explains, changes nothing, does no work, and returns next steps for the workspace, which is adequate for a read-only guide. It does not discuss permissions, authentication, rate limits, or error behavior, but those are less central for this kind of tool.

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?

The description is long, but for a guide tool the enumeration of all 13 topics is useful and each entry earns its place. The purpose and usage caveat are front-loaded before the topic list, and there is no redundant or empty filler.

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?

Given the complexity and the lack of annotations and output schema, the description is complete enough for correct invocation: it states the tool's purpose, lists all topic scopes, explains when to use it versus action tools, clarifies that it changes nothing, and notes that it returns next steps. No output schema is needed because the description explains the return context.

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 description coverage is 100%, so the baseline is 3, but the description adds real meaning beyond the enum labels by explaining what each topic covers, such as 'getting-started (clone or create an agent...)' and 'drift (changes made in the portal since the last sync...)'. The workspace parameter is left to the schema, which already describes its default, so this is a modest but genuine improvement over the schema alone.

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?

The description uses a specific verb ('Explain') and resource ('how to do one part of Copilot Studio agent development with this server's tools'), and it distinguishes itself from every sibling action tool by stating it only explains and changes nothing. An agent can immediately tell that cs_guide is a reference/help tool rather than a tool that performs work.

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?

It explicitly says to read the relevant topic when you do not know which tools a job needs or what order they go in, and it explicitly excludes cases where the user asked for something to be built, written, or run, directing the agent to call the tool that does it instead. This is a clear when-to-use and when-not-to-use statement with a named alternative class.

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