teams_send_message
Send messages to Microsoft Teams chats or channels directly from macOS AI agents.
Instructions
Send a message to a Teams chat or channel
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Send messages to Microsoft Teams chats or channels directly from macOS AI agents.
Send a message to a Teams chat or channel
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations and no description of behavioral traits (e.g., authentication, permissions, rate limits). The description completely fails to disclose what happens when invoked.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is appropriately concise with one sentence, but it omits critical information, making it insufficient rather than efficient.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's complexity (sending a message requires target specification) and the empty schema, the description is utterly incomplete. The agent has no way to use this tool correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has no parameters, but the description does not compensate by explaining how to specify the target chat or channel. The agent cannot determine what input to provide.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action 'Send' and the resource 'message to a Teams chat or channel', effectively distinguishing it from sibling tools that list or read messages.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance provided on when to use this tool over alternatives like send_email or slack_send_message, nor any context about required chat/channel identification.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/lanchuske/local-mcp-releases'
If you have feedback or need assistance with the MCP directory API, please join our Discord server