Skip to main content
Glama
AiJumpOps MCP Server

AiJumpOps MCP Server

by shariatissh

jms_asset_inspect

Inspect a JumpServer asset by name, IP, or ID to list its available system accounts and all permission rules that grant access.

Instructions

Inspect a specific JumpServer asset (by name, partial name, IP, or ID), listing its available system accounts (e.g. root, ubuntu) and all permission rules granting access to it.

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": {
      "asset": "<asset>"
    },
    "name": "jms_asset_inspect"
  }
}

Input Schema

NameRequiredDescriptionDefault
assetYesAsset name, IP address, or ID

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, the description carries the full burden; 'Inspect' implies a read but read-only status is never stated. It does usefully disclose what the call surfaces (system accounts and permission rules), yet omits key behavior for a partial-name lookup: what happens on zero or multiple matches, and whether it errors when the caller lacks access.

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 front-loaded sentence with the resource and identifier modes up front and the returned data at the end. No filler, no repetition of the tool name, and the parenthetical earns its space by enumerating accepted identifier forms.

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 single-parameter read tool with no output schema, the description covers identifier forms and the two categories of data returned, which is close to sufficient. The remaining gap is the undefined behavior of fuzzy name matching when several assets match.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning beyond the schema by disclosing that partial-name matching is supported — the schema only says 'Asset name, IP address, or ID'. That extra matching mode is genuinely useful, though the multi-match ambiguity it creates is left unexplained.

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 (Inspect) plus resource (JumpServer asset) and states the return content: system accounts and permission rules granting access. It clearly distinguishes itself from a bulk lister like jms_assets_list by scoping to 'a specific asset', though it never names a sibling tool explicitly.

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?

Usage is only implied: 'a specific asset' suggests use when you already have an identifier, versus listing all assets. There is no explicit when-to-use/when-not statement and no pointer to jms_check_access or jms_permissions_list for related questions.

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