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). 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
`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

TableJSON Schema

Name	Required	Description
`note`	No
`calls`	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"
+}

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: it discloses that direction and answered are always empty, the 50-chats/50-messages/20-pages read bound, and that truncated: true signals a cut-short read. These are non-obvious behavioral traits an agent needs to interpret results correctly.

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?

Long but dense and front-loaded: purpose, scope, exclusions, edge-case behavior, parameters, and prerequisite in order, with every clause carrying information. Slightly verbose, but no filler sentences.

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 listing tool with an output schema already present, the description covers everything an agent needs: scope, exclusions, truncation semantics, parameter format, and the account prerequisite. Nothing material 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 the schema already documents limit, since, until, and account. The description confirms the YYYY-MM-DD format and default 50, but adds little the schema does not already carry, so the baseline 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 (lists) and resource (Teams calls and meetings), plus the precise scope (50 most recent chats, newest first) and a clear exclusion ('calls outside a chat ... are not listed'). This distinguishes it cleanly from siblings like teams_read_chat_messages and teams_search_messages.

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 context: it needs a work/school M365 account connected via connect_m365_account and will not work on personal accounts. It also explains how since/until narrow the range. It stops short of naming a specific sibling alternative for the out-of-scope cases (phone calls, calendar meetings), so it is not a full 5.

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.