Skip to main content
Glama

List members and invitations

list_users
Read-onlyIdempotent

List this Project's members and the people invited to it: email, status (invited or active), the Roles each holds, and when each was last seen. Also reports live invitation_eligibility for seat-taking invitations; check it before preparing Roles or app access for a new person — a team_required restriction never applies to an Administrator-only invitation, which takes no seat and is reported as unrestricted. An unavailable offer does not prevent listing existing members.

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_users"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive behavior, and the description adds genuinely new behavior: eligibility is reported live, team_required never applies to Administrator-only invitations, and an unavailable offer does not block listing existing members. It omits pagination/result-size behavior, which matters for an unfiltered list.

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?

It is front-loaded with what gets listed, and the trailing resilience note is useful. The middle sentence is dense, packing invitation_eligibility, team_required, and the Administrator-only exception into one long clause that takes effort to parse.

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?

With no output schema, the description carries return-value disclosure and does so well, including the eligibility field and its edge cases. The only real gap is result size or pagination behavior for an unfiltered project-wide listing.

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?

The tool takes zero parameters, so the baseline is 4 and there is no parameter meaning left for the description to add. Nothing in the text misdescribes inputs.

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 ('List this Project's members and the people invited to it') and enumerates the returned fields (email, status, Roles, last seen). The read-only listing intent is unmistakable against invite_users, though no sibling is named explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives a clear usage context — check invitation_eligibility 'before preparing Roles or app access for a new person' — which positions the call as a pre-flight step. It stops short of explicit when-not guidance or naming alternatives such as invite_users.

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