Skip to main content
Glama

List team members

list_members
Read-onlyIdempotent

The people on this organization's team and the invitations still waiting for an answer. role: manager (everything; with scope "all" also the team and plan), editor (writes and schedules posts, answers comments; doesn't connect accounts or change settings) or viewer (read only). scope: "all" (every workspace, including ones added later) or the workspace ids they can open. owner: the team's owner, whose role never changes. Agents can invite viewers (invite_member), resend viewer invitations and cancel invitations; removing members and changing roles (remove_member, change_member_role) need a manager's OK in Shager first.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds value beyond that by enumerating the returned fields (members, pending invitations, role, scope, owner) and their meaning, which no output schema provides, though it omits pagination behavior or result ordering.

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 most important information, what the tool returns, is front-loaded in the first sentence. The remainder is dense but each clause (role definitions, scope definitions, owner exception, sibling authorization notes) carries distinct information, though the single run-on paragraph with inline colons could be trimmed or broken up for readability.

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?

With zero parameters and no output schema, the description does the necessary work of explaining what data comes back and what the role/scope/owner fields mean. It is missing any note about result size, pagination, or what happens when the team is large, which leaves a moderate gap for a listing tool.

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, which is the baseline-4 case. The schema coverage signal is 100% and there is nothing for the description to disambiguate at the input level; the role and scope explanations describe output fields rather than 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 opening sentence names the resource precisely: the organization's team members plus pending invitations, which is exactly what a list_members tool returns. It lacks an explicit verb like "list" and reads as a noun fragment, but an agent can still tell it apart from mutation siblings such as invite_member and remove_member, which it names.

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 resource description, and the closing sentence gives real routing context by naming invite_member, remove_member and change_member_role and noting that the latter two require a manager's OK in Shager. However, it never states an explicit condition for calling this tool (e.g., "use this to check who has access before inviting"), so the agent must infer the trigger.

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