Skip to main content
Glama
AiJumpOps MCP Server

AiJumpOps MCP Server

by shariatissh

jms_assets_list

List or search JumpServer assets by node, hostname, IP, or comment to retrieve server details such as IP address, platform, protocols, nodes, and active status.

Instructions

List or search JumpServer assets (servers/hosts) with their IP addresses, platform, protocols, nodes, and active 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_assets_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
nodeNoOptional asset node name or ID filter
limitNo
searchNoOptional search query (hostname, IP, comment)

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 burden. It usefully discloses the fields returned (a read-oriented profile), but stays silent on permission scoping (whether results are limited to assets the caller can access), pagination/truncation behavior, and the default 200 limit — all material for a listing call in an access-controlled system.

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?

A single front-loaded sentence with no filler; the resource and its scope come first and the returned attributes follow. Every clause earns its place.

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 3-parameter, read-only list tool with no output schema, the definition covers what is returned and how to filter. The gaps — pagination/limit behavior and permission-scoped visibility — are real but modest given the tool's simplicity.

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%: 'node' and 'search' are documented in the schema, and the description restates the same returned-field vocabulary rather than adding semantics. 'limit' is undocumented in both places, and the description never mentions capping results, so it adds essentially nothing beyond the schema.

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?

States a specific verb pair ('List or search') and resource ('JumpServer assets/servers/hosts'), and enumerates the fields returned (IP, platform, protocols, nodes, active status). It does not explicitly separate itself from siblings like jms_asset_inspect or jms_nodes_list, so an agent must infer the distinction, but the core purpose 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 Guidelines2/5

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

The phrase 'List or search' hints at two modes but gives no when-to-use guidance: nothing says when to prefer the 'search' query versus the 'node' filter, and no alternative sibling is named for single-asset detail. The agent is left to infer routing from the parameter names alone.

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