Skip to main content
Glama

List workspace members

clipember_list_workspace_members
Read-onlyIdempotent

Show who is in a workspace and their roles, and — for admins — the invites still waiting to be accepted. Defaults to the current workspace. To invite someone or change a role, the user does it on the Team page (https://clipember.com/team); agents can't.

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

Input Schema

NameRequiredDescriptionDefault
workspaceIdNoWorkspace id from clipember_list_workspaces; current one if omitted

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description is not required to re-state it. It earns credit instead by disclosing a permission-dependent result shape — pending invites appear only for admins — and the default workspace resolution, neither of which is in the structured fields.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two compact sentences with the capability front-loaded and the constraint/alternative trailing. Every clause carries information: what is returned, who sees the invite portion, the default target, and the out-of-scope mutations.

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 does carry the burden of describing returns, and it does so concisely (members, roles, pending invites). Minor gaps remain — nothing about result ordering, size limits, or what a caller without admin rights receives — but the tool is simple enough that this is close to complete.

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 coverage is 100% and the single optional parameter is already documented as "Workspace id from clipember_list_workspaces; current one if omitted." The description's "Defaults to the current workspace" restates that rather than adding format or resolution detail, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Show who is in a workspace and their roles") plus a scoped extension (pending invites, admins only). This is clearly distinct from clipember_list_workspaces, which enumerates workspaces rather than people inside one.

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

Usage Guidelines5/5

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

Gives an explicit when-not with the correct alternative: for inviting someone or changing a role, the description sends the agent to the Team page and states plainly that "agents can't" perform those actions. It also notes the default (current workspace), so the agent knows the parameter is optional in practice.

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