Skip to main content
Glama
AgenSysAdmin

AgenSysAdmin

by E13ctr0N

security_audit

Read-only

Run a security audit on a remote Linux server to check SSH configuration, auto-updates, failed logins, root users, and world-writable files.

Instructions

Run a comprehensive security audit: SSH config, auto-updates, failed logins, root users, world-writable files.

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": {
      "server": "<server>"
    },
    "name": "security_audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
serverYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered; the description usefully adds which categories of checks are performed. It still omits preconditions (session/connection requirement), whether it runs as root, expected duration, and how findings are surfaced, which matters for an audit spanning config files and logins.

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 a colon-delimited enumeration; every element earns its place and there is no filler.

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?

The read-only nature and check categories are adequately conveyed, but for a tool requiring a server identifier with undocumented format and no output schema, the agent still lacks information on input format, prerequisites, and result shape.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is one required parameter, 'server', with 0% schema description coverage, and the description says nothing about it - it doesn't clarify whether this is a name from list_servers, a hostname, or an ID. With no other parameter documentation anywhere, the definition fails to compensate for the coverage gap.

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 ('Run a comprehensive security audit') plus an enumerated list of checks (SSH config, auto-updates, failed logins, root users, world-writable files), which makes the scope concrete. However, it never distinguishes itself from the sibling 'full_security_audit', leaving the agent to guess which audit tool to pick.

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?

There is no when-to-use guidance, no exclusions, and no naming of the obvious alternative 'full_security_audit' or the narrower siblings (check_updates, firewall_status, check_ports). It also omits any prerequisite, such as whether the server must first be connected via connect_server.

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