Skip to main content
Glama
Office MCP Server

Office MCP Server

by hvkshetry

teams_chat

Manage Microsoft Teams chat conversations and members: list, create, update, or delete chats; send, update, or delete messages; add or remove members.

Instructions

Teams chat operations: list, create, get, update, delete chats and manage messages and members

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_chat"
  }
}

Input Schema

NameRequiredDescriptionDefault
operationYesThe operation to perform

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden and largely drops it: it does not disclose that delete/remove operations are destructive, whether deletes are recoverable, what permissions are needed, or how list operations paginate. Sections like 'manage messages and members' hide three destructive operations behind vague phrasing, leaving an agent unable to assess risk.

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?

A single front-loaded sentence with no filler and no redundancy. It is efficient, though its terseness is partly the reason so much behavioral detail is missing for a 13-operation dispatcher.

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?

A single tool multiplexing 13 operations with no annotations, no output schema, and only an 'operation' enum is a high-complexity surface that the description barely scaffolds. It never clarifies that per-operation arguments are required or what they might be, so an agent knows the menu but not how to call any specific item.

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 single 'operation' parameter is fully covered by an enum with self-descriptive values, so the schema does the heavy lifting and baseline 3 applies. The prose listing ('list, create, get, update, delete chats and manage messages and members') largely mirrors the enum rather than adding per-operation meaning, such as what a 'get' returns or whether 'update' accepts a name only.

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 names a specific resource (Teams chats) and enumerates concrete operations: list, create, get, update, delete, plus message and member management. This makes the tool's scope legible at a glance, though it offers no differentiation from the sibling teams_channel tool, which an agent could easily confuse with chat-thread operations.

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?

There is no guidance on when to choose this tool over teams_channel or the other siblings, and no indication of what each operation requires or implies. The enumeration of operations implies what can be done but gives no selection criteria or prerequisites for any of the 13 operations.

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