Microsoft Teams channel for Claude Code. An MCP stdio server that owns the Teams webhook listener, handling inbound messages from Teams and providing tools for outbound communication.
Four tools with clear names and reasonable descriptions, but significant gaps in schema completeness and parameter documentation. All tools have descriptions (10-200 chars range), but input schemas lack full type definitions and parameter descriptions are minimal. The 'react' tool is documented as non-functional (Teams API limitation), which is honest but raises questions about inclusion. No output schemas documented. Error handling guidance is absent.
Download a non-image file attachment from a Teams message. Pass the attachment_id from the inbound message. Returns the local path to the downloaded file.
Revise a message previously sent via the reply tool. Pass the message id that reply returned.
Attempt to set a reaction on a Teams message. Note: Teams allows no application to set reactions, so this tool cannot succeed. Acknowledge with a short reply instead.
Send a reply to a Teams message. Pass the conversation_id from the inbound message. For channel messages with a thread_id, set reply_to to the thread_id to answer inside that thread — never message_id, which starts a new thread beside the one you meant to answer. Omit reply_to only for a deliberate new top-level post.
Input schemas lack full type definitions and parameter descriptions. All four tools show parameter names and types in the schema, but descriptions are minimal or missing for several parameters (e.g., 'reaction' in react tool has no description beyond the parameter name).
No output schemas documented. Tool descriptions do not specify what fields are returned or their types. LLMs cannot plan downstream calls or extract required data without knowing response structure.
Error handling provides no recovery guidance. Tool descriptions lack actionable error messages or guidance on what to do if a call fails (e.g., if download_attachment fails, should the agent retry or ask the user?).
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 55 | 2026-07-28+ | v2 |
The 'react' tool is documented as non-functional ('Teams allows no application to set reactions, so this tool cannot succeed'). Including a tool that always fails violates the single-responsibility principle and wastes agent reasoning cycles.
Parameter descriptions are generic or missing context. 'text' in reply and edit_message lacks guidance on length limits, formatting, or markdown support. 'attachment_id' lacks explanation of where to obtain it or what formats are supported.