Skip to main content
Glama
mdwsk88

MS 365-21V MCP Server

by mdwsk88
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

List My Teams Chats

teams_list_chats
Read-only

List one-on-one, group and meeting Teams chats ordered by recent activity, with member names and last message. Filter by new messages or search by person or topic.

Instructions

List one-on-one, group and meeting Teams chats, most recently active first, with member names and the last message. Use since to keep only chats with new messages, and query to find a chat by person or topic. Requires delegated Chat.Read. Chinese intents / 中文意图: 查看Teams聊天, 找和某人的聊天, 最近有新消息的聊天, 查看群聊和私聊, 列出Teams会话.

Input Schema

NameRequiredDescriptionDefault
topNoMaximum chats to return, from 1 to 50. Defaults to 20.
queryNoMatch a member name, member email or chat topic. Space-separated words must all match.
sinceNoOnly chats whose last message is at or after this ISO date-time. Without an offset, China Standard Time is assumed.
cursorNonextCursor from the previous call, with the same other arguments.
chatTypeNoOnly this chat type.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.2.0
    • addedInput schema / properties / chatType
      Added value: +{
+  "description": "Only this chat type.",
+  "enum": [
+    "oneOnOne",
+    "group",
+    "meeting"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / cursor
      Added value: +{
+  "description": "nextCursor from the previous call, with the same other arguments.",
+  "maxLength": 4000,
+  "type": "string"
+}
    • addedInput schema / properties / query
      Added value: +{
+  "description": "Match a member name, member email or chat topic. Space-separated words must all match.",
+  "maxLength": 100,
+  "type": "string"
+}
    • addedInput schema / properties / since
      Added value: +{
+  "description": "Only chats whose last message is at or after this ISO date-time. Without an offset, China Standard Time is assumed.",
+  "maxLength": 40,
+  "type": "string"
+}
    • changedInput schema / properties / top / description
      Previous value: -"Number of chats to return, from 1 to 50."New value: +"Maximum chats to return, from 1 to 50. Defaults to 20."
  2. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

With readOnlyHint and openWorldHint already declared, the description adds real context: the required delegated Chat.Read scope, the sort order, and the fact that each result carries member names and a last-message preview. Pagination behavior itself is left to the schema's cursor field rather than explained.

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?

Front-loaded with the operation and ordering, then parameter guidance, then a short prerequisite. The Chinese intent list is longer than strictly necessary but serves genuine multilingual intent matching. No wasted sentences aside from that block.

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?

For a read-only list tool with no output schema, the description supplies what the schema cannot: the shape of each returned item (member names, last message), the ordering, auth requirements, and filter intent. Nothing an agent needs to invoke it correctly is missing.

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 coverage is 100%, so the baseline is 3, but the description adds interpretive value beyond the schema text: 'since' is framed as 'keep only chats with new messages' rather than only an ISO timestamp bound, and 'query' as finding a chat by person or topic. 'top' and 'cursor' are left to the schema, which documents them adequately.

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?

States a specific verb and resource ('List ... Teams chats'), names the covered chat kinds (one-on-one, group, meeting), and specifies ordering ('most recently active first') plus returned fields (member names, last message). That scope cleanly separates it from teams_list_chat_messages, which lists messages inside a chat.

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

Usage Guidelines4/5

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

Explicitly routes parameter choice: 'Use since to keep only chats with new messages, and query to find a chat by person or topic.' It also surfaces the delegated Chat.Read prerequisite. It never names the sibling teams_list_chat_messages as the alternative for reading message contents, so there is a gap at the boundary.

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