Skip to main content
Glama

list_users

List your organization's users and filter by role, status, or name/email search. Large result sets are stored and summarized to keep responses concise.

Instructions

List users of your organization, optionally filtered by role, status or a name/email search. Large result sets are stored and summarized.

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
roleNo
searchNoMatches name or email.
statusNo
max_resultsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it does disclose the non-obvious trait that "Large result sets are stored and summarized," which hints that results may be truncated and retrievable via list_stored_results/read_stored_result. However, it never says what threshold triggers storage, how to retrieve the stored payload, whether the call is read-only, or how max_results interacts with this behavior.

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 sentences, front-loaded with purpose and followed by the salient behavioral caveat. No filler or redundant wording.

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?

For a 4-parameter tool with no annotations, no output schema, and sparse schema documentation, the description is minimally adequate: it names the filters and warns about large-result handling. It is missing what the response actually looks like, how to get the stored full results, and what max_results does, all of which an agent needs to call this correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 25% (only `search` is documented), so the description needs to compensate. It restates the three filter dimensions already named in the schema and adds no semantics for the enum values (admin/instructor/learner, active/inactive) or for `max_results` (default 100, max 5000), which is entirely unaddressed despite governing the "stored and summarized" behavior.

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 users of your organization") plus the available filters, which is enough to distinguish it from get_user and list_training_participants. It stops short of explicitly contrasting itself with those siblings, so it lands just below the top score.

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 filter list (use it when you want users narrowed by role, status, or a name/email search), but there is no explicit when-to-use or when-not-to-use guidance and no mention of get_user as the single-record alternative. An agent must infer the selection logic.

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