send_chat_message
Send a direct message to a Teams chat by providing the chat ID and message content.
Instructions
Send a direct chat message
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| chatId | Yes | Chat ID | |
| message | Yes | Message content |
Send a direct message to a Teams chat by providing the chat ID and message content.
Send a direct chat message
| Name | Required | Description | Default |
|---|---|---|---|
| chatId | Yes | Chat ID | |
| message | Yes | Message content |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description bears full burden for behavioral traits. It only states 'Send a direct chat message', omitting details such as permissions, mutation side effects, error handling, or reply behavior.
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 a single sentence, front-loaded with the key action. It is concise, though it could include a bit more detail without becoming verbose.
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 no output schema or annotations, the description is incomplete. It does not explain return values, error conditions, or prerequisites, leaving an AI agent underinformed for a direct action tool.
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?
Schema coverage is 100%, and parameter descriptions are clear ('Chat ID', 'Message content'). The tool description adds no additional meaning beyond the schema, so baseline score is appropriate.
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 verb 'Send' and specifies 'direct chat message', which distinguishes it from the sibling 'send_channel_message'. However, it does not explicitly differentiate beyond the word 'direct'.
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 is provided on when to use this tool versus alternatives like 'send_channel_message'. The description lacks any context about appropriate scenarios or exclusions.
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/eesb99/office365-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server