Skip to main content
Glama
AiJumpOps MCP Server

AiJumpOps MCP Server

by shariatissh

jms_user_action

Inspect a user's permissions or perform lifecycle actions such as enable, disable, group changes, and creation. Mutating actions require a preview with confirm=false before confirmation.

Instructions

Inspect a user's permissions, or perform a user lifecycle action (enable, disable, add-to-group, remove-from-group, create). For mutating actions, ALWAYS call with confirm=false first!

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

Input Schema

NameRequiredDescriptionDefault
nameNoNew user display name (when action=create)
userNoTarget username, display name, email, or ID
emailNoNew user email (when action=create)
groupNoTarget User Group (for add-to-group, remove-from-group, or create)
actionNoinspect
confirmNoSet to true ONLY after the user explicitly confirms the preview.
usernameNoNew username (when action=create)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden, and it does disclose the important preview-then-confirm safety workflow for mutations. It omits other behavioral facts an agent needs: required privileges, whether disable is reversible, and what an 'inspect' call actually returns. Useful but not complete for a mixed read/write tool.

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 short sentences, front-loaded with the capability and immediately followed by the critical safety rule. No filler or redundancy.

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 7-parameter, mixed read/write tool with no annotations and no output schema, the definition covers the action model and the confirm workflow but leaves side effects, permission requirements, and inspect output unexplained. Adequate to call correctly in the common path, but not fully self-contained.

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 86%, so the schema already explains each parameter, including confirm and the create-only fields. The description only adds the grouping of actions and the ordering constraint on confirm, which the schema's own confirm text largely restates. Baseline 3 is appropriate.

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 set and an enumerated set of lifecycle actions (inspect, enable, disable, add-to-group, remove-from-group, create), so the agent knows exactly what the tool does. It stops short of distinguishing itself from closer siblings such as jms_permission_grant/revoke or jms_users_list, which is the only thing keeping it off a 5.

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

Usage Guidelines4/5

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

It gives a concrete, actionable rule for the danger case: mutating actions must first be called with confirm=false. That is real when-to-do-what guidance. There is no explicit routing to sibling tools (e.g. for listing users or granting individual permissions), so the alternative-selection guidance is incomplete.

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