Skip to main content
Glama
zb-ss

Servonaut

by zb-ss
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_server_memory

Retrieve cached OS, runtime, service, web-stack, and log summaries for a managed instance before SSH; if missing, build memory first.

Instructions

Return cached memory (OS, runtimes, services, web stack, logs) for a managed instance. Call FIRST before issuing SSH commands — the cached summary frequently answers OS/runtime/service/web-stack questions without an SSH round-trip. If this returns an error with code='missing', the server has no memory yet — call build_server_memory(instance_id) to probe and populate it, then retry this tool. format='summary' (default) gives a token-efficient Markdown digest; format='markdown' gives the full untruncated version; format='full' returns the raw JSON for all modules; format='context_block' returns a envelope identical to what the first-party Servonaut chat client injects — use this when you want a single drop-in block to prepend to your own model context; format='stack_summary' returns a compact JSON stack profile (os, docker presence, databases, web server, log paths) for detector recon — the cheapest per-scan projection. Note: format='full' returns structured per-module data (observed, declared, probed_at, ttl_seconds, sudo_used, truncated, partial, raw_output). raw_output is scrubbed of secrets by the redaction library when config.memory.redaction_enabled is true (default).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
formatNoOutput format (default: summary).summary
instance_idYesInstance ID or name. '<account>/<name>' picks the server of one provider account; custom servers are 'custom/<name>'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.28.0
    • changedInput schema / properties / instance_id / description
      Previous value: -"Instance ID, name, or custom-server name."New value: +"Instance ID or name. '<account>/<name>' picks the server of one provider account; custom servers are 'custom/<name>'."
  2. Addedv2.24.0
  3. Removedv2.23.8
  4. Changed1 schema field changedv2.23.0
    • changedInput schema / properties / format / enum
      Previous value: -[
-  "summary",
-  "full",
-  "markdown",
-  "context_block"
-]New value: +[
+  "summary",
+  "full",
+  "markdown",
+  "context_block",
+  "stack_summary"
+]
  5. First observedv1.0.0

TDQS

A4.9/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so: it discloses the error contract (code='missing'), the redaction behavior of raw_output (config.memory.redaction_enabled default true), and the structured field set returned for format='full'. This is far beyond a restatement of the name.

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?

Front-loaded with the critical 'call FIRST' guidance, which is the right structure. The format enumeration is long and slightly dense, but nearly every clause maps to a distinct decision an agent must make, so little is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, yet the description fully characterizes the return content per format (Markdown digest, raw JSON modules, drop-in context block, compact stack profile) plus failure handling. An agent has everything needed to call correctly.

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

Parameters5/5

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

Schema coverage is 100%, but the description goes well beyond the schema's terse 'Output format (default: summary).' by explaining what each of the five enum values produces and when to pick each — genuine added semantics.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Return cached memory ... for a managed instance') and enumerates the covered domains (OS, runtimes, services, web stack, logs). It clearly distinguishes itself from build_server_memory and refresh_server_memory by being the read/cached accessor.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Explicitly instructs 'Call FIRST before issuing SSH commands' and gives the exact failure path: on error code='missing', call build_server_memory(instance_id) then retry. It also conditions format choice on intent (detector recon, model context, full data).

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

Deploy Server

Other Tools