Skip to main content
Glama
Office MCP Server

Office MCP Server

by hvkshetry

teams_meeting

Create, update, cancel, and find Microsoft Teams meetings, and retrieve transcripts, recordings, participants, and insights through the Office MCP Server.

Instructions

Teams meeting operations: create, update, cancel, find, list transcripts, get recordings, and more

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": {
      "operation": "<operation>"
    },
    "name": "teams_meeting"
  }
}

Input Schema

NameRequiredDescriptionDefault
operationYesThe operation to perform

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It signals that some operations mutate state (create, update, cancel) but does not disclose permissions, side effects, irreversibility of cancellation, or what the operations return.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single sentence is concise and front-loads the resource, but 'and more' is vague and the operation list is incomplete. For an eleven-operation tool, this structure is efficient but under-informative.

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

Completeness2/5

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

The tool supports eleven distinct operations with no annotations and no output schema, so the description should explain operation-specific behavior or requirements. Instead it gives only a partial capability list, leaving an agent unable to distinguish operation semantics from the enum alone.

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?

The schema has 100% description coverage and an enum fully enumerating the operation values, so the baseline is 3. The description names several operations but omits get, get_transcript, get_participants, and get_insights, and adds no operation-specific input semantics beyond the enum itself.

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 resource, Teams meetings, and names several concrete operations such as create, update, cancel, and transcript/recording retrieval. It is distinguishable from sibling resources like teams_channel and teams_chat, though 'and more' and the omission of several enum operations soften the precision.

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

Usage Guidelines2/5

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

It lists capabilities but gives no explicit guidance on when to use this tool versus alternatives such as calendar, nor when to choose one operation over another. The closest thing to guidance is the operation list itself, which implies usage only weakly.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.