Skip to main content
Glama
Sign In
teams-chat-mcp

teams-chat-mcp

by hanshengcc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_messages

Read-only

Read messages from a Microsoft Teams conversation, oldest first, with optional date filter and message limit. Use it to review chat history by conversation ID, exact name, or partial name.

Instructions

Read messages from one Teams conversation, oldest first.

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": {
      "conversation": "<conversation>"
    },
    "name": "get_messages"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoNewest N messages to return (1-1000)
sinceNoOnly messages on/after this date, e.g. 2026-10-01
conversationYesConversation id, exact name, or unique part of the name

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered; the description adds the useful ordering trait ('oldest first'). However it doesn't reconcile that ordering with the limit parameter's 'Newest N messages' behavior, nor mention pagination limits, which leaves a real behavioral question unanswered.

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

Conciseness4/5

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

A single front-loaded sentence with no filler. It is efficient but arguably over-compressed for a tool with ordering subtleties worth one more clause.

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?

An output schema exists, so return values needn't be explained, and annotations cover the safety profile. Still missing: how the 'oldest first' ordering interacts with limit/since and whether large histories are truncated — gaps an agent would want resolved before calling.

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

Parameters3/5

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

Schema description coverage is 100%, so all three parameters (limit, since, conversation) are already documented including formats and ranges. The description adds only the ordering semantics, which actually sits in mild tension with the limit field's 'newest N' wording rather than clarifying it.

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

Purpose4/5

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

Names a specific verb+resource ('Read messages') and scopes it to 'one Teams conversation,' which implicitly separates it from the cross-conversation sibling search_messages. It stops short of explicitly naming any sibling, so it doesn't earn a 5.

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?

'from one Teams conversation' hints that this is the single-conversation read path, implying search_messages is for cross-conversation lookup, but no when-to-use or when-not-to-use guidance is stated outright. An agent must infer the routing decision from the sibling name alone.

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