Local MCP

Teams Send Channel Message

teams_send_channel_message

Sends a text message to a Microsoft Teams channel via Graph API. Requires connect_m365_account with Chat.ReadWrite / ChannelMessage.Send permissions. team_id and channel_id must come from teams_list_teams / teams_list_channels. First call returns a preview; set confirm=true to send.

Input Schema

TableJSON Schema

Name	Required	Description
`text`	Yes	Plain-text message body
`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.
`confirm`	No	Set true to send; false returns preview
`team_id`	Yes	Team ID from teams_list_teams, or the team's name
`channel_id`	Yes	Channel ID from teams_list_channels, or the channel's name

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field 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"
+}

Changed2 schema fields changedAug 13, 2026

changedInput schema / properties / channel_id / description

Previous value: -"Channel ID from teams_list_channels"New value: +"Channel ID from teams_list_channels, or the channel's name"

changedInput schema / properties / team_id / description

Previous value: -"Team ID from teams_list_teams"New value: +"Team ID from teams_list_teams, or the team's name"

First observedJun 30, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=false and openWorldHint=true, but the description adds genuinely new behavior: the required auth/permission scopes and, most importantly, the preview-then-confirm flow. It doesn't cover failure modes or rate limits, so it is not exhaustive.

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?

Three tight sentences, front-loaded with the action, then prerequisites, then the safety-relevant confirm behavior. No filler or redundancy.

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 values need not be described. Between annotations (openWorld, non-destructive), the schema, and the description's permission and confirm guidance, an agent has everything needed to call this correctly.

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 text, account, confirm, team_id and channel_id. The description's references to ID sources and confirm=true largely restate what the schema already says, which is the expected baseline-3 outcome.

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 ('Sends a text message to a Microsoft Teams channel') plus the transport ('via Graph API'). The 'channel' scoping cleanly separates it from the sibling teams_send_message (chat) without needing to name it.

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 concrete prerequisites (connect_m365_account with Chat.ReadWrite / ChannelMessage.Send) and tells the agent where team_id and channel_id must come from (teams_list_teams / teams_list_channels). It does not explicitly state when to prefer a sibling such as teams_send_message, so it stops short of a 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.