Skip to main content
Glama

List Teams

list_teams
Read-only

List the Microsoft Teams you belong to and optionally fetch all result pages to review complete team membership.

Instructions

List teams you are a member of

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": "list_teams"
  }
}

Input Schema

NameRequiredDescriptionDefault
fetch_all_pagesNoFetch all pages of results (max 50 pages)

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?

The annotation readOnlyHint=true already establishes the safe-read profile, so the description's main added value is the membership restriction, which is real behavioral context (results are scoped to the caller, not tenant-wide). It says nothing about pagination defaults or ordering even though fetch_all_pages implies a paged result set, leaving the default volume of returned teams undisclosed.

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?

One short, front-loaded sentence with no waste or filler. It is efficient, though the brevity borders on under-specification rather than optimal density.

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 trivial one-parameter read tool with annotations covering safety and a fully documented parameter, the core is present. The gap is that the description never tells the agent what comes back (no output schema exists) or whether the default call returns all teams or a first page, which affects how the tool should be invoked.

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?

The single parameter has full schema description coverage ('Fetch all pages of results (max 50 pages)'), and the description adds nothing about it. With coverage at 100%, the baseline of 3 applies since the schema already carries the meaning.

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 ('List') and resource ('teams') and adds a meaningful scope qualifier, 'you are a member of', which distinguishes it from a hypothetical list-all-teams operation. It does not name any sibling, so the agent must infer the boundary with list_groups or list_users from names alone.

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: the membership scope hints at when this is the right tool (finding teams the caller belongs to), but there is no explicit when-to-use, when-not-to-use, or pointer to an alternative tool. For a simple read tool this is minimally viable rather than helpful.

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