Local MCP

Teams List Channels

teams_list_channels

Read-only

Lists the channels of a Microsoft Teams team (team_id from teams_list_teams), by name, from Microsoft 365. The channel id feeds teams_read_channel_messages. Reads at most 20 pages of channels. 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.
`team_id`	Yes	Team ID from teams_list_teams

Output Schema

TableJSON Schema

Name	Required	Description
`note`	No
`count`	No
`error`	No
`account`	No	The email (UPN) of the Microsoft 365 account this call used.
`channels`	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.

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

Changed1 schema field changedJul 30, 2026
- changedInput schema / properties / team_id / description
```
Previous value: -"Team ID from list_teams"New value: +"Team ID from teams_list_teams"
```
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 readOnlyHint/openWorldHint/destructiveHint annotations, the description discloses a concrete pagination bound ('at most 20 pages'), the truncation signal ('truncated: true') when cut by that bound or by timeout, and an authentication constraint (work/school account only; personal accounts have no Teams reads). This is exactly the extra behavioral context annotations cannot carry.

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?

Three sentences, front-loaded with purpose and scope, with each clause carrying real information (provenance, downstream link, page bound, truncation, auth). Slightly dense mid-sentence parentheticals keep it from a full 5.

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 shape needn't be explained, yet the description still supplies the truncation semantics, pagination bound, and auth requirements an agent needs to call and interpret the tool correctly. 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 both parameters are already documented in the schema; the description only reinforces team_id's origin (from teams_list_teams). Baseline 3 is appropriate when the schema does the heavy lifting.

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 channels of a Microsoft Teams team... from Microsoft 365') and disambiguates from siblings by naming teams_list_teams as the team_id source and teams_read_channel_messages as the consumer of the returned channel id. An agent can place this tool in the workflow chain without opening another schema.

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 prerequisite context ('team_id from teams_list_teams') and the downstream use ('channel id feeds teams_read_channel_messages'), plus the account prerequisite via connect_m365_account. It clearly says when the tool fits but does not explicitly name exclusions or platform alternatives (e.g. slack_list_channels).

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.