Reads messages from a Microsoft Teams channel. Use team and channel IDs from teams_list_channels to retrieve conversations.
Reads messages from a Microsoft Teams channel (team_id and channel_id from teams_list_channels).
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v3.0.165v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are supplied, so the description carries the full behavioral-disclosure burden. It only says 'Reads' and does not describe pagination, return format, authentication requirements, rate limits, or whether all or recent messages are returned.
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?
Single sentence, front-loaded with the action and resource, and the parenthetical prerequisite is compact. No filler or repetition.
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?
For a messaging-read tool with no annotations, no output schema, and an empty input schema, the description is too thin. It omits invocation details for the referenced IDs, pagination/return behavior, and any constraints, leaving key context gaps.
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?
Parameter count is 0 and schema coverage is 100%, so the baseline is 4. The description adds source context for team_id and channel_id from teams_list_channels, although those IDs do not appear in the empty input schema.
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?
States a specific verb (Reads) and resource (messages from a Microsoft Teams channel), and differentiates channel reads from chat reads via the channel qualifier and sibling teams_read_chat_messages. It also names teams_list_channels as the source of the required IDs.
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?
Provides an implied prerequisite (obtain team_id and channel_id from teams_list_channels), but does not state when to choose this over teams_read_chat_messages, teams_search_messages, or other read tools, nor any exclusions or constraints.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.