Skip to main content
Glama
Sign In
chatwatch

chatwatch

by xxxxDev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

teams_read_messages

Read the last N messages from a Microsoft Teams chat by title, title fragment, or ID without marking the chat as read.

Instructions

Read the last n messages of a chat (title, title fragment or id) without marking it read.

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": {
      "chat": "<chat>"
    },
    "name": "teams_read_messages"
  }
}

Input Schema

NameRequiredDescriptionDefault
nNo
chatYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden and does disclose one non-obvious behavioral trait: the read does not mark the chat as read, which matters for side-effect expectations. It omits ordering of results, what happens on ambiguous title fragments or unknown chats, and any permission requirements.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler; every clause (scope, identifier forms, read-status side effect) adds information.

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

Completeness3/5

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

For a simple two-parameter read with no output schema, the essentials are present, but gaps remain around result ordering/format, the default value of n, and behavior when the chat string matches multiple chats.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate: it explains that "chat" accepts a full title, a title fragment, or an id, which the bare string schema does not. "n" is only implicitly defined as a count of messages (capped at 50 by the schema), leaving its default unspecified.

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

Purpose5/5

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

States a specific verb and resource ("Read the last n messages of a chat") plus the scope of identification (title, title fragment, or id). The scope wording separates it from siblings like teams_list_chats and teams_wait_for_messages without needing to name them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied by the phrase "read the last n messages" — an agent can infer this is for fetching recent history rather than waiting for new messages, but the description never names teams_wait_for_messages as the alternative or states when not to use this tool.

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