Skip to main content
Glama

get_server_memory

Fetches cached server memory (OS, runtimes, services, web stack, logs) for a managed instance, answering system questions without SSH round-trips. Call first before running commands.

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, name, or custom-server name.
Behavior4/5

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

No annotations provided, so description carries full burden. Discloses read-only nature, error code 'missing', format specifics, and redaction of secrets. Could be more transparent about additional error conditions or performance, but is quite detailed overall.

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?

Description is front-loaded with main purpose and usage guidance, then details formats. Every sentence adds value, though length is substantial. Could be slightly more concise but structure is good.

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?

No output schema exists, so description compensates by explaining return formats and fields (e.g., for 'full' format). Covers error handling, redaction, and format-specific projections. Missing minor details like size limits or additional error codes, but overall complete for the tool's complexity.

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

Parameters4/5

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

Schema description coverage is 100%, baseline 3. Description adds value by explaining each format's purpose and use case beyond the schema's enum values, and clarifies that instance_id accepts ID, name, or custom-server name.

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?

The description clearly states the tool returns cached memory (OS, runtimes, services, web stack, logs) for a managed instance. It distinguishes from siblings by advising 'Call FIRST before issuing SSH commands' and directing to build_server_memory when memory is missing.

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 to call this tool first before SSH commands. Provides error handling: if error code 'missing', call build_server_memory then retry. Also details each format's use case (e.g., 'context_block' for prepending to model context, 'stack_summary' for detector recon).

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/zb-ss/servonaut'

If you have feedback or need assistance with the MCP directory API, please join our Discord server