Skip to main content
Glama
Sign In
Copilot Desktop MCP

Copilot Desktop MCP

by avianhermana
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

List Meeting Summaries

list_meeting_summaries
Read-only

Lists all meeting recordings with generated summary.md files, so you can find available meeting summaries.

Instructions

List all meeting recordings that have generated summary.md files.

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": "list_meeting_summaries"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so safety is covered; the description's added value is the filtering rule ('have generated summary.md files'). It does not say whether results are ordered, paginated, or how many recordings may be returned, and the presence of an output schema covers return shape.

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?

A single sentence, front-loaded with verb and resource, with the filter condition attached and no filler. Nothing could be removed without losing information.

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?

For a no-parameter, read-only listing tool with an output schema and clear annotations, the description supplies what is needed to select and call it. The main residual gap is any indication of result volume or ordering, which the output schema may already imply.

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?

Zero parameters, so there is no parameter meaning to convey; the baseline is 4. Schema coverage is 100% and the description correctly does not invent arguments.

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 (list) and a specific resource (meeting recordings) with a meaningful qualifier: only those that have generated summary.md files. That qualifier distinguishes it from a generic listing tool and from recording-status tools in the sibling set, 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 — an agent can infer 'use this to discover which meetings already have summaries' — but there is no explicit when-to-use, when-not-to-use, or pointer to alternatives such as a status or directory-listing tool.

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