Local MCP

Teams Call History

teams_call_history

Read-only

Lists the Microsoft Teams calls and meetings that ended in the account's 50 most recent chats, newest first, from Microsoft 365: call type (call, meeting or screenShare), participants, start and end times and duration. Calls outside a chat (phone calls, calendar meetings without a chat) are not listed, and Microsoft does not say who started a call or whether it was answered: direction and answered are always empty. Optional since/until (YYYY-MM-DD) narrow the range. Looks at the 50 most recent chats and, in each, at its newest 50 messages that are not deleted (reading at most 20 pages of 50). A chat the account cannot read (403 or 404) is skipped and counted in skipped_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). 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 calls to return (default 50), newest first
`since`	No	Only calls on/after this date, YYYY-MM-DD (optional)
`until`	No	Only calls on/before this date, YYYY-MM-DD (optional)
`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

Name	Required	Description
`note`	No
`calls`	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
`truncated`	No	Present and true only when the read was cut before it had everything it was asked for.
`skipped_chats`	No	How many chats were skipped because the account cannot read them (403 or 404). Present only when above 0.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 22, 2026

addedOutput schema / properties / skipped_chats

Added value: +{
+  "description": "How many chats were skipped because the account cannot read them (403 or 404). Present only when above 0.",
+  "type": "integer"
+}

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

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

addedOutput schema / properties / account

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

addedOutput schema / properties / calls / items / properties / participants / items
```
Added value: +{
+  "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"
+}

AddedJul 1, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Goes well beyond the readOnly/openWorld annotations: discloses the scan bounds (50 chats × newest 50 non-deleted messages, max 20 pages), that unreadable chats are skipped and surfaced in skipped_chats, that truncation yields truncated: true, the 403/404 handling, and the auth prerequisite (work/school M365 via connect_m365_account; personal accounts unsupported). It also explains the local-cache fallback, its staleness and Full Disk Access requirement, and that the source field reveals which backend answered.

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-loads what it is and its scope, then layers caveats and fallback behavior. It's dense as a single paragraph, but nearly every sentence carries operational value – direction/answered always empty, truncation, cache staleness.

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, yet the description still pre-empts confusion by explaining the empty direction/answered fields, skipped_chats, truncated and source. Given the fallback paths and auth requirements, an agent has everything needed to call it and interpret the result.

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 the schema already documents all four parameters. The description reinforces since/until as YYYY-MM-DD range filters and mentions the default newest-first ordering, but adds little beyond the schema and says nothing about limit or account.

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, resource and scope: lists Teams calls and meetings from the account's 50 most recent chats, newest first, with the fields returned. This is clearly distinguishable from siblings like teams_list_chats or teams_search_messages, which don't return call records.

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?

Makes the exclusion explicit – calls outside a chat (phone calls, calendar meetings without a chat) are not listed – which tells an agent when this tool won't help. It doesn't name an alternative tool for those cases, so it stops short of full when/when-not routing.

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.