mcp-github-enterprise

List teams

list_teams

Read-onlyIdempotent

Retrieves an organization's teams and their slugs, privacy, and permissions so you can select the correct team slug for follow-up team tools.

Instructions

List an organization's teams with their slugs, privacy, and permissions. Use a team slug with the team tools.

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

Input Schema

Name	Required	Description	Default
`org`	Yes	Organization login (must be within GHE_ORG_ALLOWLIST when that is set)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Nov 7, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds that slugs, privacy, and permissions are surfaced, a useful hint about the payload, but says nothing about pagination, result size, or what an empty list means.

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?

Two short sentences with the primary purpose front-loaded and no filler. The trailing usage sentence is slightly under-specified ('the team tools'), which costs it a perfect score, but nothing is redundant.

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?

For a single-parameter, read-only list operation with full schema documentation and no output schema, this covers what the agent needs: what it lists, what fields come back, and how results are consumed. Only the follow-up tool names and pagination behavior are left implicit.

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?

Only one parameter with 100% schema coverage, and the schema already documents the org login and the GHE_ORG_ALLOWLIST constraint. The description's 'an organization's teams' merely restates the scoping implied by the parameter name, adding no format or allowlist detail beyond the schema.

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 an organization's teams') plus the fields returned (slugs, privacy, permissions), which distinguishes it from sibling list tools like list_members and list_organizations. It stops short of naming any sibling explicitly, so it lands just below the top tier.

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?

The second sentence ('Use a team slug with the team tools') gives downstream context on what the results are for, which implies usage. However, it does not say when to prefer this over alternatives or name the specific team tools, and 'the team tools' is vague given no sibling here has an obvious team-name match.

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