Skip to main content
Glama

list_workspace_users

Read-onlyIdempotent

Lists workspace members with roles, online status, and recent activity. Use it to find who is on the team or check what someone last worked on.

Instructions

Members of the current workspace: id, name, role, online/last seen, and what each one last worked on.

include_contact=True adds phone/email (personal data: only when the user actually needs it).

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

Input Schema

NameRequiredDescriptionDefault
include_contactNo
include_deletedNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare this a safe, idempotent, read-only operation, so the bar is lower. The description adds a genuine privacy/behavioral note about personal data exposure on include_contact, but says nothing about what 'include_deleted' does to the result set or how it interacts with the listed fields (e.g., whether deleted members appear with contact data).

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, front-loaded sentences with no filler; the returned-fields list comes first and the parameter caveat is isolated in a parenthetical. Minor cost: the line break mid-sentence across 'online/last seen, and what each one last worked on' reads as formatting noise rather than structure.

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 simple two-boolean listing tool with an output schema and full safety annotations, very little is required; the description covers scope, payload fields, and the sensitive-parameter rule. The remaining gap is include_deleted, whose semantics an agent cannot infer from any source.

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 0%, so the description must carry parameter meaning. It explains include_contact well — both the payload (phone/email) and the gating rule — but include_deleted is never mentioned, leaving one of two parameters completely undocumented in both schema and description.

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 names the resource precisely ('Members of the current workspace') and enumerates the returned dimensions (id, name, role, online/last seen, last activity), which clearly distinguishes it from workspace-level siblings like list_workspaces or switch_workspace. It is stated as a noun phrase rather than a verb, but the tool name supplies the verb unambiguously.

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?

There is no explicit when-to-use guidance for the tool itself and no named alternative (e.g., get_user_workload, which also involves per-user data). The only conditional guidance is for a parameter: 'include_contact=True ... only when the user actually needs it', which is a useful but narrow usage rule.

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