Skip to main content
Glama

graph_reply_to_channel_message

Sends a reply to a specific Microsoft Teams channel message using team, channel, and message IDs.

Instructions

Reply to a channel message.

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_id": "<message_id>",
      "message": "<message>"
    },
    "name": "graph_reply_to_channel_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
is_htmlNo
messageYes
team_idYes
mentionsNo
channel_idYes
message_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.10.0

TDQS

C2.2/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 disclosure burden and provides almost none. It implies a mutation (creating a reply) but says nothing about permissions, whether the reply is visible channel-wide or thread-only, or how mentions or is_html affect rendering.

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 short sentence is technically concise and front-loaded, but its brevity comes from omission rather than economy; there is no wasted wording because there is almost no wording at all.

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

Completeness2/5

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

For a six-parameter mutation tool with no annotations, no output schema, and zero schema descriptions, the definition is far too thin. An agent could not reliably construct the mentions payload or know whether is_html should be toggled off for plain text.

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 six parameters, including non-obvious ones such as 'mentions' (nullable array of arbitrary objects) and 'is_html' (defaulting true). The description explains none of them, leaving required IDs and the message payload completely undocumented.

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

Purpose3/5

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

The description states a verb ('Reply') and a resource ('channel message'), which is slightly more specific than the tool name and implies a threaded response versus a top-level post. However, it adds nothing about scope, thread semantics, or how it differs from graph_send_channel_message beyond the word 'reply'.

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 when-to-use guidance, no mention of when a plain channel message is preferable to a reply, and no prerequisites stated. The only hint is the verb itself, which an agent must interpret on its own.

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