Skip to main content
Glama
AgenSysAdmin

AgenSysAdmin

by E13ctr0N

full_security_audit

Read-only

Run an automated security audit on a remote Linux server and get a score, grade, findings, and markdown report covering SSH, firewall, users, network, services, updates, logs, kernel, and malware.

Instructions

Run a comprehensive security audit with scoring: SSH, firewall, users, network, filesystem, services, updates, logs, kernel, malware. Returns score, grade, findings, and markdown report.

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": "full_security_audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
serverYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3/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 the safety profile is covered; the description usefully adds the output shape (score, grade, findings, markdown report). It omits operationally relevant behavior for an audit of this breadth: whether it connects to a remote host, whether elevated privileges are needed, and roughly how long ten domain scans take.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the verb and scope, followed by the return contract. The ten-item enumeration is dense but each item conveys real audit coverage; nothing is padded or redundant.

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?

With no output schema, the description does the right thing by naming the return payload (score, grade, findings, markdown report). However, for a broad, likely long-running remote audit with an undocumented required parameter, the definition leaves the agent without identifier format or execution expectations.

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 a single required parameter, 'server', with 0% schema description coverage, and the description supplies no meaning for it at all — no indication whether it takes a hostname, an ID from list_servers, or a session handle. With the schema doing nothing, the description needed to compensate here and does not.

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 and resource ('Run a comprehensive security audit') and enumerates the ten covered domains (SSH, firewall, users, network, filesystem, services, updates, logs, kernel, malware), which implicitly subsumes the granular sibling checks like check_ports and firewall_status. It stops short of explicitly contrasting itself with those single-area checks, so an agent must infer the relationship.

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 word 'comprehensive' hints that this is the broad sweep, but the description never states when to choose it over the individual check_* tools, nor any when-not conditions, prerequisites, or runtime expectations. No explicit alternative is named even though the sibling set contains obvious overlapping candidates.

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