Skip to main content
Glama

assess_infrastructure

Read-only

Assess VPS health in one pass: inspect OS, kernel, uptime, load, RAM, storage headroom, containers, systemd, services, databases, and migrations, then return a health verdict and warnings.

Instructions

One-shot comprehensive VPS infrastructure assessment.

Inspects OS distribution, kernel architecture, uptime, compute load averages (1m/5m/15m), RAM utilization, storage volume headroom (<15% free triggers warnings), container runtimes (Docker/Podman), systemd health, managed services breakdown, allowlisted databases, and active migration rehearsals. Emits an overall health verdict ('healthy', 'degraded', 'critical') and actionable operational warnings.

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

Input Schema

NameRequiredDescriptionDefault
include_servicesNo
include_databasesNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.1

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false with openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavioral detail beyond that: the specific threshold that triggers warnings (<15% free storage) and the three-tier verdict it emits ('healthy', 'degraded', 'critical'), which is the kind of output-shaping context annotations cannot convey.

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, both earning their place: the first front-loads the scope, the second enumerates coverage and outputs. The long comma-separated inventory is dense but appropriate for a comprehensive scan tool; minor cost is that the verdict/threshold information arrives after the inventory rather than being front-loaded.

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?

An output schema exists, so return values need not be explained, and annotations cover the safety profile; the description focuses correctly on scope and verdict semantics. What remains thin is the meaning of the two boolean toggles, which is the one gap an agent would need to close before invoking it with non-default arguments.

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 description coverage is 0% and neither include_services nor include_databases carries a description, so the schema gives no meaning for the two booleans. The description partially compensates by naming 'managed services breakdown' and 'allowlisted databases' as sections of the assessment, implying what the flags toggle, but it never states that these parameters control those sections or what happens when they are false.

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 pair ('comprehensive VPS infrastructure assessment') and then enumerates the exact domains inspected (OS, kernel, load averages, RAM, storage headroom, container runtimes, systemd, services, databases, migration rehearsals). That enumeration lets an agent distinguish it from narrow siblings like db_inspect or service_inspect, though it never names a sibling explicitly to draw the contrast.

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?

'One-shot comprehensive' implies a first-pass triage use case, and the breadth of the enumeration signals it is the aggregate check rather than a targeted probe. However, there is no explicit when-to-use versus when-to-use-an-alternative guidance (e.g. use service_inspect for a single service instead), so the routing decision is left to inference.

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