Skip to main content
Glama
Systems Manager

Systems Manager

List Users

sm_user_list_users
Read-onlyIdempotent

Lists users in the system so AI agents can inspect accounts and support user and group management tasks.

Instructions

List users (sm_user_operations). Operations for user and group management

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.2.11

TDQS

C2.8/5.0
Behavior2/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=true, so the safety profile is supplied externally. The description adds nothing beyond that: it does not say whether all users are returned unpaginated, what fields each user record contains, or whether the call needs elevated privileges on a remote host.

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

Conciseness3/5

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

It is short and front-loaded, but the second sentence does not earn its place — it describes a namespace, not the tool. Brevity here comes from under-specification rather than tight editing.

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?

This is a simple zero-parameter listing tool whose safety semantics are covered by annotations, so the bar is low. Still, with no output schema the agent gets no hint of the return shape (user names, UIDs, home directories) or result size, which is the one thing the description could have usefully added.

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 and the schema coverage is reported as 100%, so there is no parameter semantics for the description to carry. The baseline for a no-parameter tool applies.

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

Purpose3/5

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

The first sentence names a clear verb and resource ("List users"), but it is essentially a restatement of the title. The trailing clause "Operations for user and group management" describes the parent namespace rather than this tool, and it muddies the boundary with the sibling sm_user_list_groups instead of clarifying it.

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

Usage Guidelines2/5

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

There is no guidance on when to use this versus sm_user_list_groups or any other listing tool, and no stated preconditions or exclusions. The agent must infer the selection rule entirely from the tool name.

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

Deploy Server

Other Tools