Skip to main content
Glama

List teams

team_list
Read-only

List the organization's teams: each one's id, slug, title, description and members (userId, and whether they are a maintainer or a member of the team), and the wikis it is granted (wikis: name and level, of those the caller may see). Joining a team opens its wikis at those levels.

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": {
      "org": "<org>"
    },
    "name": "team_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
orgYesslug of the organization whose people, teams and access to use. Required on every call, even when only one organization is listed; a path never names it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / org / description
      Previous value: -"slug of the organization whose people, teams and access to read. Required on every call, even when only one organization is listed; a path never names it."New value: +"slug of the organization whose people, teams and access to use. Required on every call, even when only one organization is listed; a path never names it."
  2. Added

TDQS

A3.7/5.0
Behavior4/5

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

With readOnlyHint and destructiveHint=false already declaring the safety profile, the description still adds real behavioral context: the exact result shape (id, slug, title, description, members with maintainer/member status, granted wikis with name and level) and the filtering rule that only wikis visible to the caller are returned. It also explains the consequence of team membership ("Joining a team opens its wikis at those levels"), which is semantics not captured anywhere in the schema.

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 listing purpose is front-loaded and the field enumeration and membership note follow in a logical order with no filler. The single dense sentence with nested parentheticals is slightly hard to scan, which keeps it below a 5.

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, so the description carries the burden of describing results — and it does, field by field, including nested member and wiki details plus the visibility caveat. For a one-parameter read-only listing tool, that is essentially complete; only ordering/pagination behavior is unaddressed.

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% for the single required `org` parameter, and the schema already states it is required on every call and that paths never name it. The description adds nothing about `org`, so the baseline 3 applies — no gap, but no added meaning either.

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+resource ("List the organization's teams") and enumerates the fields returned, so the agent knows exactly what this returns. It is implicitly distinguishable from team_get and members_list, but it never names a sibling or says how it differs from fetching a single team.

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?

Read-only listing usage is implied by "List" and by the annotations, and the visibility caveat ("of those the caller may see") hints at permission-dependent results. There is no explicit when-to-use/when-not guidance, e.g. no statement that this returns all teams and team_get should be used for a single team's details.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources