Skip to main content
Glama

graph_send_channel_message

Send a message to a Microsoft Teams channel by specifying the team, channel, and message content.

Instructions

Send a message to a channel.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "team_id": "<team_id>",
      "channel_id": "<channel_id>",
      "message": "<message>"
    },
    "name": "graph_send_channel_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
is_htmlNo
messageYes
team_idYes
mentionsNo
channel_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.10.0

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden of behavioral disclosure. It conveys only that this is a write operation; it says nothing about required permissions, the default HTML body handling (is_html defaults to true), how mentions are rendered, whether messages are editable afterward, or rate limits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single sentence is front-loaded and free of filler, which is good. The brevity, however, reads as under-specification rather than discipline, since nothing useful beyond the tool's name is communicated.

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

Completeness1/5

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

For a mutating tool with five undocumented parameters, no annotations, and no output schema, the description should explain input shapes and side effects. It does neither, leaving an agent unable to construct a correct call from the description alone.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across five parameters, and the description adds no meaning for any of them. It never explains what team_id versus channel_id identify, what the message string accepts, or what the free-form mentions object should contain.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb ('Send') and a specific resource ('a message to a channel'), so an agent knows exactly what operation this performs. It does not, however, distinguish this from the sibling graph_send_chat_message, so the channel-vs-chat boundary is left implicit.

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

Usage Guidelines2/5

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

There is no guidance on when to use this versus graph_send_chat_message, graph_reply_to_channel_message, or graph_send_mail, all of which appear in the sibling list. No preconditions, no exclusions, and no note about when a reply tool would be more appropriate.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools