Skip to main content
Glama

graph_send_chat_message

Send messages to Microsoft Teams chats with HTML or plain text, optional mentions, importance levels, and subject lines.

Instructions

Send a message to a chat.

Args: chat_id: The chat ID. message: Message body. When is_html is true, send explicit HTML; markdown is not converted. is_html: Whether the body is HTML content (default: True). Use false for plain text. mentions: Optional mentions. Each entry accepts raw Graph mention fields or a simplified shape with name/display_name and user_id. importance: Message importance: "normal", "high", or "urgent" (default "normal"). subject: Optional subject line. Empty omits it.

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": {
      "chat_id": "<chat_id>",
      "message": "<message>"
    },
    "name": "graph_send_chat_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
chat_idYes
is_htmlNo
messageYes
subjectNo
mentionsNo
importanceNonormal

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.10.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden and does add real behavioral detail: the default of is_html=true, the fact that markdown is NOT converted when is_html is true, and that an empty subject omits the field. It omits what an agent still needs for a write operation — required permissions/scopes, whether the send is immediate or idempotent, error conditions, and what the response contains (e.g., message id).

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?

The operative sentence is front-loaded before the Args block, and each argument line is compact and non-redundant. The block is somewhat long for six parameters but every line except the chat_id line contributes new meaning.

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

Completeness3/5

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

For a mutation tool with zero annotations and no output schema, parameter documentation is thorough but the operational envelope is thin — nothing about auth requirements, failure modes, or what is returned after sending. An agent can construct a correct call but cannot anticipate the result or permission errors.

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

Parameters4/5

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

Schema description coverage is 0%, so the description must compensate, and it largely does: every one of the six parameters is addressed, including defaults for is_html, importance, and subject, the enum values for importance, and the accepted shapes for mentions (raw Graph fields or a simplified name/display_name plus user_id form). The weakest entry is chat_id, which is only restated as 'The chat ID' and gives no format hint (id vs. email-style identifier).

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 first line gives a specific verb and resource — 'Send a message to a chat' — which lets an agent separate it from channel, mail, or reply tools by the 'chat' target. It stops short of naming the nearest sibling (graph_send_channel_message) or stating the chat-vs-channel distinction explicitly, so it is clear but not fully differentiated.

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 choose this over graph_send_channel_message, graph_send_mail, or graph_reply_to_channel_message, and no prerequisites or exclusions. The only directional cue ('Use false for plain text') is about a parameter, not about tool selection.

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