Skip to main content
Glama

graph_list_chats

Retrieve recent Microsoft Teams chats, with options to limit results and continue paging through older conversations.

Instructions

List recent Microsoft Teams chats.

Args: top: Maximum number of chats to return (default 50, maximum 50). next_link: Opaque nextLink URL from a previous call, used to fetch the next page. Overrides the other paging arguments when supplied. include_next_link: Whether to wrap the result as {items, next_link} so paging can continue (default false, which returns a bare list).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "graph_list_chats"
  }
}

Input Schema

NameRequiredDescriptionDefault
topNo
next_linkNo
include_next_linkNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.10.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It discloses the paging behavior and both return shapes (bare list vs {items, next_link}) plus the default page size, which is genuinely useful. It omits ordering semantics for "recent", auth requirements, and rate limits. It also claims a maximum of 50 while the schema permits far larger values, leaving the effective cap ambiguous.

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?

The one-line purpose statement is front-loaded and the Args block is compact and scannable. Each parameter note adds information rather than restating the schema. Slightly verbose line wrapping but no filler.

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

Completeness4/5

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

There is no output schema, and the description correctly compensates by explaining the two possible return shapes, which is the key thing an agent must know to page. What a chat object contains and the ordering of results are unstated, but for a simple list-with-paging tool the coverage is close to sufficient.

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 is the only source of parameter meaning, and it covers all three: what top does and its default, that next_link is an opaque URL from a prior call that overrides other paging args, and that include_next_link switches the return shape. Only the conflicting maximum value for top keeps this from a 5.

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?

States a specific verb and resource ("List recent Microsoft Teams chats"), which separates it from sibling list tools about chats' members or messages. The word "recent" adds a scope hint. It stops short of naming any sibling or clarifying how it differs from related chat operations, so it is clear but not differentiating.

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?

There is no statement of when to use this tool versus alternatives, nor prerequisites such as required permissions. The parameter notes do implicitly describe a two-step paging workflow (call first without next_link, then pass next_link, optionally with include_next_link). That is useful operational guidance but not tool-selection guidance.

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