Skip to main content
Glama
Sign In
Copilot Desktop MCP

Copilot Desktop MCP

by avianhermana
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Start Meeting Recording

start_meeting_recording

Start recording meeting audio locally from Teams, Zoom, or web conferences, capturing speakers, microphone, or both as timestamped PCM WAV files.

Instructions

Start recording meeting audio from Microsoft Teams, Zoom, or web conferences.

source: 'both' (Speakers/Attendees + Microphone), 'system' (Speakers only), or 'mic' (Microphone only).

Audio is recorded locally in PCM WAV format with timestamps.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "start_meeting_recording"
  }
}

Input Schema

NameRequiredDescriptionDefault
labelNo
sourceNoboth
max_minutesNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

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, and it does disclose useful traits: audio is captured locally, in PCM WAV, with timestamps. It omits the important behaviors — where the file is written, whether recording runs in the background, what happens when max_minutes is reached, and what permissions the capture requires.

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 short, front-loaded lines: purpose first, then the mode mapping, then output format — no filler. The backtick-marked parameter callout is scannable, though the format sentence could be tightened.

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?

Return values are covered by the output schema, so the description needn't explain them. But for a mutation-style tool with zero annotations, it leaves the agent without key context: file destination, background-vs-blocking behavior, failure modes, and how the recording is terminated.

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 0% and there are no enums in the schema, so the description must compensate; it does so well for `source`, spelling out the three modes ('both', 'system', 'mic') and what each captures. However, `label` and `max_minutes` (default 120) are never explained, leaving the recording-length cap undocumented.

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?

The description states a specific verb and resource ('Start recording meeting audio') and scopes the sources it works with (Microsoft Teams, Zoom, web conferences). Against the sibling 'stop_meeting_recording' the paired naming makes the distinction obvious without needing schema reads, though no sibling is named explicitly.

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?

Usage is only implied: the agent can infer this should be called when a meeting begins in a supported conferencing app, and that 'stop_meeting_recording' likely ends it. There is no explicit when-to-use, when-not-to-use, or statement of prerequisites/permissions.

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