Local MCP

Teams List Chats

teams_list_chats

Read-only

Lists the Microsoft Teams chats of a Microsoft 365 account — direct messages, group chats and meeting chats — most recently active first, read from Microsoft 365 (not from this Mac's Teams app). Each chat has its id (for teams_read_chat_messages), a title, the other participants, its type (oneOnOne, group or meeting) and its last message. Reads at most 20 pages of 50 chats. When the read is cut (by that bound, or because the call ran out of time) the answer has truncated: true. Needs a work or school Microsoft 365 account connected with connect_m365_account (personal Microsoft accounts have no Teams reads).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No	Max items to return (default 50)
`account`	No	Which connected Microsoft 365 account to use: its email (UPN), its id from list_m365_accounts, or its display name when unique. Leave it out to use the default account.

Output Schema

TableJSON Schema

Name	Required	Description
`note`	No
`chats`	No
`count`	No
`error`	No
`account`	No	The email (UPN) of the Microsoft 365 account this call used.
`truncated`	No	Present and true only when the read was cut before it had everything it was asked for.

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedOct 5, 2026

addedInput schema / properties / account

Added value: +{
+  "description": "Which connected Microsoft 365 account to use: its email (UPN), its id from list_m365_accounts, or its display name when unique. Leave it out to use the default account.",
+  "type": "string"
+}

changedInput schema / properties / limit / description

Previous value: -"Max chats to return (default 50)"New value: +"Max items to return (default 50)"

addedOutput schema / properties / account

Added value: +{
+  "description": "The email (UPN) of the Microsoft 365 account this call used.",
+  "type": "string"
+}

addedOutput schema / properties / note
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / truncated

Added value: +{
+  "description": "Present and true only when the read was cut before it had everything it was asked for.",
+  "type": "boolean"
+}

First observedJun 30, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Beyond the annotations (readOnly/openWorld/non-destructive), the description discloses the data source caveat (read from M365, not the local Mac app), the pagination bound (20 pages of 50 chats), and the truncation signal (truncated: true) with its two triggers. This is exactly the behavioral context annotations cannot convey.

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?

Purpose is front-loaded and each subsequent sentence carries distinct value (fields, pagination, truncation, auth). The single long first sentence is slightly dense, but nothing is redundant.

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?

With an output schema present, return values need no explanation, and the description still covers the remaining gaps: auth prerequisites, source of truth, and truncation behavior. Nothing an agent needs to call it correctly is missing.

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 description coverage is 100%, so both limit and account are already fully documented in the schema. The description adds no extra semantics for these two parameters, so the baseline of 3 applies.

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 (lists Microsoft Teams chats) and enumerates the covered subtypes (direct, group, meeting), clearly distinguishing it from sibling tools like teams_list_channels and teams_list_teams. An agent can identify both what it returns and how it differs from neighbors.

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?

Gives an explicit prerequisite (a work/school M365 account connected via connect_m365_account, noting personal accounts are unsupported) and routes to teams_read_chat_messages for the next step. It lacks an explicit when-not statement against chat-listing siblings, but the context is clear enough to select correctly.

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

All Local MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.