Skip to main content
Glama
AiJumpOps MCP Server

AiJumpOps MCP Server

by shariatissh

jms_users_list

Lists or searches JumpServer users and returns their username, email, role, groups, active status, and 2FA/MFA status, with optional filters by user group and search query.

Instructions

List or search JumpServer users with their username, email, role, groups, active status, and 2FA/MFA status.

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

Input Schema

NameRequiredDescriptionDefault
groupNoOptional User Group name or ID filter
limitNo
searchNoOptional search query (username, name, email)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden; it does establish that this is a non-mutating read and discloses the fields returned, which is meaningful. It says nothing about pagination behavior (despite a limit default of 200), permissions required, or whether results are capped/truncated.

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?

A single front-loaded sentence with no filler; the verb+resource leads and the field list follows. Slightly ambiguous in that the same sentence mixes filtering concepts with returned attributes, but nothing is wasted.

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 3-parameter, zero-required read tool with no annotations and no output schema, the description usefully stands in for the missing output schema by naming returned fields. It is still incomplete on filter interaction (search vs group), result limits, and pagination, which an agent needs to call it correctly.

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 67%, and the two documented parameters (group, search) already explain their own scope in the schema. The description adds no semantics beyond restating that search exists, and the undocumented limit parameter gets no explanation of default page size or how to paginate.

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 a specific verb pair (list/search) and resource (JumpServer users), and enumerates the fields carried per user (username, email, role, groups, active status, 2FA/MFA), so an agent knows what it will get. It stops short of distinguishing itself from siblings such as jms_user_action or jms_user_groups_list.

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?

"List or search" implies two usage modes (unfiltered enumeration vs query) but gives no explicit when-to-use/when-not guidance and never points at an alternative tool. An agent can infer it is the read path for users, but must reason about jms_user_action vs this tool on its own.

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