Skip to main content
Glama

Local MCP

by com.local-mcp
OverviewDiscussionsAdmin

Teams Send Channel Message

teams_send_channel_message
Destructive

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

NameRequiredDescriptionDefault
textYesPlain-text message body
accountNoWhich 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.
confirmNoSet true to send; false returns preview
team_idYesTeam ID from teams_list_teams, or the team's name
rememberNoWith confirm: true, also stop asking for this kind of action from now on. Only when the person said so ("don't ask again"). The person can revoke it in LMCP or with set_always_allowed.
channel_idYesChannel ID from teams_list_channels, or the channel's name

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / remember
      Added value: +{
+  "description": "With confirm: true, also stop asking for this kind of action from now on. Only when the person said so (\"don't ask again\"). The person can revoke it in LMCP or with set_always_allowed.",
+  "type": "boolean"
+}
  2. Changed1 schema field changed
    • 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"
+}
  3. Changed2 schema fields changed
    • 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"
  4. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Goes beyond annotations by disclosing the two-phase call flow (first call returns a preview, confirm=true actually sends) and the required account/permission setup — exactly the kind of context the destructiveHint alone doesn't convey. It stops short of saying the message is visible to all channel members and cannot be unsent, which is why destructiveHint=true is set.

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 short sentences, no filler, front-loaded with what the tool does, then prerequisites, then the confirm flow. Every sentence carries information an agent needs before calling.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive, open-world write tool with an output schema and rich parameter docs, the description covers purpose, auth, ID provenance, and the safety-relevant confirm gate. Minor gap: no note on the irreversibility/audience of the sent message, which is the main risk of a destructiveHint=true tool.

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 team_id, channel_id, confirm, account, and remember are all already documented in the schema. The description restates the ID sourcing and confirm semantics but adds no formats, constraints, or edge cases (e.g. name-vs-ID ambiguity, remember behavior) beyond the schema. Baseline 3 applies.

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 (send a text message to a Teams *channel*) and names the backing API. The channel scope implicitly but clearly separates it from the sibling teams_send_message (chat-scoped), and it names the discovery tools that supply the IDs.

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 preconditions: connect_m365_account with Chat.ReadWrite/ChannelMessage.Send, and team_id/channel_id must come from teams_list_teams/teams_list_channels. It also documents the required preview-then-confirm workflow. It does not explicitly exclude the chat variant (teams_send_message), which would have made this 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 toolsInspect
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.

Resources