Skip to main content
Glama
Obsideo MCP server

Obsideo MCP server

by Regan-Milne

Back up the credentials and encryption key

backup_keys
Idempotent

Copies account recovery data—credentials, signing key, encryption key, and upload commitments—to a specified archive or directory, preserving recoverability if local files are lost.

Instructions

Copy everything needed to recover this account's data (credentials, account signing key, encryption key, upload commitments) to a destination: one you are already authorized to use for backups, or one your human names. Obsideo holds no copy of the encryption key: if the local file is lost, encrypted objects are unrecoverable no matter how many providers hold them. Until this has been run, the only copy is on this machine, so it is worth running once after the account is created and again after any signup that rotates keys. A .tar.gz path produces one archive; a directory path produces plain copies. With no destination it refuses rather than choosing one.

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

Input Schema

NameRequiredDescriptionDefault
destinationNoArchive path ending in .tar.gz, or a directory. Required: there is no default location.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.7.7
    • changedInput schema / properties / destination / description
      Previous value: -"Archive path ending in .tar.gz, or a directory; defaults to ~/obsideo-keys-<account>-<date>.tar.gz"New value: +"Archive path ending in .tar.gz, or a directory. Required: there is no default location."
  2. Addedv0.7.2

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare non-read-only, idempotent, non-destructive, closed-world, but the description adds genuinely new context: no server-side copy of the encryption key exists, data is unrecoverable if the local file is lost, and the tool refuses without a destination. It does not describe what the call returns or how failures beyond a missing destination are surfaced, which keeps it short of a 5.

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?

The core action is front-loaded in the first clause, and the operational warnings follow logically. There is some redundancy: 'Obsideo holds no copy of the encryption key: if the local file is lost, encrypted objects are unrecoverable' and 'Until this has been run, the only copy is on this machine' convey overlapping urgency, costing a little tightness.

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?

For a single-parameter tool with full schema coverage and annotations covering the safety profile, the description supplies the crucial recovery/loss context and destination constraints. The main omission is any indication of what the call returns or confirms on success, which matters somewhat since no output schema exists.

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 100% and the schema already explains that destination is an archive path ending in .tar.gz or a directory with no default. The description restates the archive-versus-directory semantics and the refusal behavior, which is useful reinforcement but adds little meaning beyond the schema — baseline 3 applies.

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 concrete verb and resource — copy everything needed to recover the account's data (credentials, signing key, encryption key, upload commitments) to a destination. The scope is precise enough that it is unmistakably distinct from sibling storage tools like put, get, ls, or rm.

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?

Gives explicit timing advice (run once after account creation, again after any signup that rotates keys) and constrains the destination to one already authorized for backups or one named by the human. It also states the failure mode — no destination means it refuses rather than picking one — so the agent knows exactly what conditions to satisfy before calling.

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