create_snapshot
Create full system snapshot with one-command rollback script. Returns snapshot location, file count, and RESTORE.sh path.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Nervous System
TDQS
A3.6/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations indicate it is not read-only and not destructive, but the description does not elaborate on potential side effects, execution time, or required permissions. Minimal additional value beyond annotations.
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?
Extremely concise with two sentences. Front-loads the core action and returns. No wasted words.
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?
Covers the essential inputs (none) and outputs, but could benefit from mentioning when to create a snapshot (e.g., before system updates) to improve completeness.
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?
No parameters exist, so schema coverage is 100%. The description effectively explains what the tool does and what it returns, which is sufficient for a parameterless tool.
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?
Clearly states the action (create), resource (full system snapshot), and key outputs (rollback script, location, file count, RESTORE.sh path). Distinguishes from sibling tools that are audits or checks.
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?
No explicit guidance on when to use this tool, prerequisites, or alternatives. The description implies it is for creating snapshots but does not advise on context or limitations.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
A3.7/5.0
Disambiguation4/5
Most tools have clearly distinct purposes, but there is some overlap among multiple audit/check tools (e.g., accountability_check, drift_audit, security_audit). However, descriptions and naming help differentiate their specific scopes, so ambiguity is low.
Naming Consistency5/5
All tool names follow a consistent verb_noun pattern in snake_case (e.g., check_archive_safety, propagate_family_member), making them predictable and easy to understand.
Tool Count4/5
33 tools is on the high side, but the server covers a broad domain (system health, audits, propagation, session management, etc.). The count is justified by the comprehensive scope, though it may feel heavy for agents.
Completeness5/5
The tool set covers the entire lifecycle of system management: health monitoring, audits, propagation, sessions, compliance, and more. No obvious gaps for the stated purpose of a nervous system framework.