Skip to main content
Glama
AiJumpOps MCP Server

AiJumpOps MCP Server

by shariatissh

jms_asset_create

Register a new server asset in JumpServer with hostname, address, protocol, and platform. Preview the plan first, then confirm to create it safely.

Instructions

Register/create a new server asset in JumpServer. Always call with confirm=false first to preview and ask user confirmation!

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": {
      "name": "<name>",
      "address": "<address>"
    },
    "name": "jms_asset_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesServer hostname / asset name
nodeNoTarget asset tree node name or ID
portNoProtocol port (e.g. 22 for SSH, 3389 for RDP)
addressYesServer IP address or FQDN
commentNo
confirmNoSet to true ONLY after the user explicitly confirms the previewed plan.
platformNoPlatform name (Linux, Windows, etc.)Linux
protocolNoConnection protocol (ssh, rdp, vnc, telnet)ssh

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 bears the full disclosure burden. It does add real value by describing the two-phase filter: a preview call and then a confirm call. However, it doesn't explain what the preview returns, what permissions are required, whether the operation is reversible, or what happens on confirm. Covering the safety flow but omitting the result behavior earns a middle score.

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?

It consists of two short sentences, with the purpose first and the safety workflow second. Every sentence carries information that is directly useful for calling the tool. Nothing is redundant with the tool name or title.

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 an unannotated mutation tool with eight parameters and no output schema, the most critical missing piece (the confirmation workflow) is covered. The description does not cover expected outcomes, error conditions, or what effect creation has on the asset tree. It is adequate but leaves clear gaps for an agent operating without annotations.

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 88%, so the schema already defines all eight parameters well. The description adds a little meaning to the confirm flag by tying it to a preview/confirmation workflow. It does not explain the required name/address pairing or the relationship between node, platform, and protocol.

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 uses a specific verb+resource ("Register/create a new server asset in JumpServer"), which clearly separates it from read-only siblings like jms_asset_inspect and jms_assets_list. It does not name any sibling explicitly, so it falls short of the 5 benchmark, but the intent is unmistakable.

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 operating rule: call with confirm=false first to preview and ask the user for confirmation. That is actionable context an agent needs for a mutation tool. It stops short of 5 because it doesn't say when not to use it (e.g., when the asset already exists, use inspect first) or name alternative tools.

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