Skip to main content
Glama

graph_list_teams

Lists Microsoft Teams the authenticated user has joined, with optional next-link wrapping so you can page through results.

Instructions

List Microsoft Teams that the authenticated user has joined.

Args: 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_teams"
  }
}

Input Schema

NameRequiredDescriptionDefault
next_linkNo
include_next_linkNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.10.0

TDQS

A3.5/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 behavioral burden and does disclose useful defaults: a bare list by default, and an opt-in {items, next_link} envelope for paging. It does not cover auth/permission requirements, ordering of results, page size, or whether the call is read-only (all graph_list_* siblings suggest it, but that is inference rather than statement).

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?

Purpose is front-loaded in the first sentence, and the Args block is limited to the two parameters that actually exist. The wording is slightly padded by the docstring-style header and repeated default notation, but nothing is off-topic.

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 two-parameter read tool with no output schema and no annotations, the definition covers paging mechanics well and explains the two possible return shapes. It leaves out permission/auth context and any characterization of the returned team objects, which an agent would otherwise have to discover by calling.

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, and it does: next_link is described as an opaque URL from a prior call that overrides the other paging arguments, and include_next_link is tied to the concrete return shape with its default spelled out. Only minor gaps remain, such as next_link's expected format beyond "opaque" and that it is optional/empty by default.

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?

The description opens with a specific verb and resource plus an explicit scope: "List Microsoft Teams that the authenticated user has joined." That scope distinguishes it from roster-style siblings like graph_list_team_members, but it never names an alternative, so a reader must infer the boundary themselves.

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 implied by the scope phrase "that the authenticated user has joined," which tells the agent this returns only the caller's own teams. There is no when-to-use/when-not-to-use statement, no named alternative for enumerating all teams in a tenant, and no prerequisites such as required permissions.

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