Skip to main content
Glama
AiJumpOps MCP Server

AiJumpOps MCP Server

by shariatissh

jms_auth_otp

Completes a pending JumpServer 2FA/TOTP challenge after MFA_OTP_REQUIRED is returned, submitting the user's 6-digit authenticator code to finish authentication.

Instructions

Complete a pending 2FA/TOTP authentication challenge when JumpServer returns MFA_OTP_REQUIRED, using the 6-digit code provided by the user.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "code": "<code>"
    },
    "name": "jms_auth_otp"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYes6-digit TOTP code from the user's Authenticator app

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/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 usefully discloses the precondition of a pending challenge and that the code comes from the user's authenticator app, but says nothing about failure behavior (invalid code, expiry), rate limiting, or what the caller should do after success.

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?

One sentence, front-loaded with the trigger condition, with every clause contributing information. Nothing extraneous.

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 one-parameter auth step with no output schema, the description covers purpose, trigger, and input source adequately. Only post-success and error-path expectations are left unstated.

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 100% and the single code parameter is fully documented there, so baseline 3 applies. The description's mention of the 6-digit user-provided code largely restates the schema rather than adding new semantic detail.

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

Purpose5/5

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

States a specific verb (complete) and resource (pending 2FA/TOTP authentication challenge) plus the exact trigger condition (JumpServer returns MFA_OTP_REQUIRED). No sibling tool in the catalog handles authentication, so the purpose is unambiguous and distinguishable.

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?

The when-to-use condition is explicit and actionable: only after a MFA_OTP_REQUIRED response. It gives no when-not guidance, but the trigger is narrow enough that few alternatives could be confused with it.

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