Skip to main content
Glama
AgenSysAdmin

AgenSysAdmin

by E13ctr0N

generate_report

Read-only

Creates a markdown report with system information, disk usage, open ports, and services for a remote Linux server.

Instructions

Generate a comprehensive markdown report: system info, disk usage, ports, services.

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

Input Schema

NameRequiredDescriptionDefault
serverYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.3/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 adds the output format (markdown) and section list, which is real value, but says nothing about whether a server session must be connected first, how long an aggregate run takes, or whether sections can be scoped.

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, no repetition of the tool name, no filler beyond the mild '-comprehensive'. Every word identifies either the action, the output format, or the report contents.

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 one parameter and no output schema, the description should carry the load, and it does explain the return shape (markdown with four sections). It falls short on the required 'server' argument's expected value and on any prerequisite connection state, which matter for an aggregation tool in a session-based server family.

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?

Schema description coverage is 0% for the single required 'server' parameter, and the description never mentions it. An agent must guess whether 'server' is a name from list_servers, a hostname, or an ID, and whether a session must be active for it.

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?

A specific verb ('Generate') plus a specific artifact ('comprehensive markdown report') with the enumerated contents (system info, disk usage, ports, services). This makes it clearly the aggregate counterpart to siblings like system_info and disk_usage, though the description never states that relationship 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: an agent can infer the tool is for getting everything at once rather than calling the individual check tools. There is no explicit when-to-use, when-not-to-use, or named alternative (e.g., 'use system_info for just host details').

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