Skip to main content
Glama
Sign In
Helios

Helios

by brazaoo4
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

export_bundle

Idempotent

Create a crash-safe portable backup archive of the SQLite memory database and Markdown exports without locking concurrent readers or writers, for server backups and migration snapshots.

Instructions

Create or overwrite a portable backup archive (helios_portable_bundle.tar.gz) on the server filesystem. Uses the SQLite Online Backup API to capture a crash-safe snapshot of memory.db alongside all Markdown exports without locking concurrent readers or writers, leaving database records untouched. Use export_bundle for server backups and migration snapshots; use get_client_setup_bundle instead to generate IDE/CLI configuration snippets, or recall_memories to query stored facts.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.8.3

TDQS

A4.9/5.0
Behavior5/5

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

Annotations only declare the safety profile (readOnly=false, destructive=false, idempotent=true); the description adds real substance beyond that — the overwrite behavior of an existing archive, the SQLite Online Backup API mechanism, crash-safety, non-blocking concurrency, and that DB records are untouched. These are exactly the traits an agent needs to judge risk and side effects.

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?

Three sentences, front-loaded with the action and artifact, then mechanism/behavior, then sibling routing. No filler or restated name/title.

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?

An output schema exists, so return values need not be described. With annotations covering safety, the description adds mechanism, overwrite semantics, concurrency guarantees, and alternatives — nothing an agent needs in order to invoke it correctly is missing.

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?

Zero parameters, so there is nothing for the description to disambiguate; the baseline for a no-param tool applies. The description instead specifies the implicit output target (a fixed archive path on the server filesystem), which is a useful non-schema detail.

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 artifact: 'Create or overwrite a portable backup archive (helios_portable_bundle.tar.gz) on the server filesystem.' This is a distinct resource from every sibling (get_client_setup_bundle produces config snippets, recall_memories queries facts), so an agent can route correctly without opening schemas.

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 names the positive case ('server backups and migration snapshots') and two named alternatives with their own use cases — get_client_setup_bundle for IDE/CLI config, recall_memories for querying facts. Both when-to-use and when-not-to-use are covered.

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