Local MCP

Teams Read Channel Messages

teams_read_channel_messages

Read-only

Reads the most recent posts of a Microsoft Teams channel (team_id from teams_list_teams, channel_id from teams_list_channels), oldest first, from Microsoft 365. Top-level posts only: replies are not included. Reading channel messages needs a permission that an administrator of the Microsoft 365 organization approves; without it the answer is consent_required and says what to do. body is the whole message up to 20,000 characters; a longer one is cut there and its row has body_truncated: true. Reads at most 20 pages of 50 posts, deleted ones included. 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). When no Microsoft 365 account is connected at all, it reads the Teams app's local cache on this Mac instead (needs Full Disk Access, can be hours or days behind); the answer's source says which one answered (graph or local_cache).

Input Schema

Name	Required	Description
`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.
`team_id`	Yes	Team ID from teams_list_teams
`channel_id`	Yes	Channel ID from teams_list_channels

Output Schema

Name	Required	Description
`note`	No
`count`	No
`error`	No
`source`	No	Which source answered: graph (Microsoft 365) or local_cache (the Teams app's cache on this Mac, used only when no Microsoft 365 account is connected).
`account`	No	The email (UPN) of the Microsoft 365 account this call used.
`fix_tool`	No
`messages`	No
`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.

Changed1 schema field changedOct 24, 2026
- addedOutput schema / properties / messages / items / properties / body_truncated
```
Added value: +{
+  "type": "boolean"
+}
```

Changed2 schema fields changedOct 10, 2026

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

addedOutput schema / properties / source

Added value: +{
+  "description": "Which source answered: graph (Microsoft 365) or local_cache (the Teams app's cache on this Mac, used only when no Microsoft 365 account is connected).",
+  "enum": [
+    "graph",
+    "local_cache"
+  ],
+  "type": "string"
+}

Changed6 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 messages (default 50)"New value: +"Max items to return (default 50)"

changedInput schema / properties / team_id / description

Previous value: -"Team ID"New value: +"Team ID from teams_list_teams"

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

Changed1 schema field changedJul 30, 2026

changedInput schema / properties / channel_id / description

Previous value: -"Channel ID from list_teams_channels"New value: +"Channel ID from teams_list_channels"

First observedJun 30, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Adds substantial behavior beyond the annotations: admin consent behavior and consent_required, top-level-only exclusion of replies, 20,000-character body truncation with body_truncated, a 20-page-by-50-post cap, inclusion of deleted posts, and a truncated flag when results are cut. It also discloses the graph versus local_cache source and the Full Disk Access requirement for cache reads.

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?

The purpose is front-loaded in the first sentence, and the remaining sentences each carry distinct operational caveats. Despite its length, every sentence adds useful behavior for a complex read path, including permission, truncation, pagination, account, and fallback details.

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?

An output schema exists, and the description covers the material invocation context: permission failure behavior, pagination and truncation, account prerequisites, local-cache fallback, and the source indicator. Nothing important needed to call the tool correctly appears to be 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?

The schema already documents all four parameters at 100% coverage, including limit, account, team_id, and channel_id. The description reinforces team_id and channel_id provenance and account prerequisites but does not add much parameter-specific meaning beyond the schema, so the baseline of 3 is appropriate.

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: reads the most recent posts of a Microsoft Teams channel. It also distinguishes the scope by noting top-level posts only and naming where team_id and channel_id come from, so an agent can identify this tool apart from chat or search tools.

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 clear prerequisites: team_id from teams_list_teams, channel_id from teams_list_channels, an admin-approved permission, and a connected work/school account. It also explains the local-cache fallback when no Microsoft 365 account is connected, but it does not explicitly route to sibling alternatives such as teams_read_chat_messages or teams_search_messages.

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.