Local MCP

Teams List Teams

teams_list_teams

Read-only

Lists the Microsoft Teams teams the Microsoft 365 account belongs to, by name. Start here for channels: the team id feeds teams_list_channels and teams_read_channel_messages. (For direct and group chats use teams_list_chats.) Reads at most 20 pages of teams. 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
`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
`count`	No
`error`	No
`teams`	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.

Changed4 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 / 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.6/5.0

Behavior5/5

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

Annotations cover the safety profile (readOnly, non-destructive, openWorld), and the description goes well beyond them: it discloses the 20-page read bound, the truncated: true signal when the read is cut or times out, and the authentication prerequisite that only work/school M365 accounts work (personal accounts have no Teams reads). That is unusually rich behavioral context for a read tool.

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 every sentence carries distinct information (routing, alternative, pagination bound, truncation signal, auth prerequisite). It is dense and slightly long, but no sentence is filler; only minor tightening is possible.

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, so return-value shape need not be explained, yet the description still documents the truncation flag. Combined with the auth prerequisite and downstream tool routing, nothing an agent needs to call this 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% and there is only one optional parameter, so the schema already documents the account selector fully. The description adds no format or syntax detail about the account parameter. Baseline 3 is correct.

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 the Microsoft Teams teams the Microsoft 365 account belongs to, by name') and explicitly distinguishes itself from the chat-oriented sibling: '(For direct and group chats use teams_list_chats.)'. An agent can tell it apart from teams_list_channels and teams_list_chats without opening a schema.

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

Usage Guidelines5/5

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

Gives explicit routing guidance: 'Start here for channels: the team id feeds teams_list_channels and teams_read_channel_messages', plus the exclusion pointing to teams_list_chats for direct/group chats. This is a clear when-to-use plus named alternatives.

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.