Skip to main content
Glama

mnemon_create_snapshot

Creates a persistent point-in-time storage snapshot of a database cluster branch, so you can preserve branch state for recovery or testing.

Instructions

Create a persistent point-in-time storage snapshot of a database cluster branch.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "tenant_id": "<tenant_id>"
    },
    "name": "mnemon_create_snapshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoOptional snapshot identifier label
branch_idNoBranch to snapshot (default: main)
tenant_idYesDatabase tenant identifier

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.6

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description carries the full burden, and it discloses only that the snapshot is 'persistent' and 'point-in-time'. It says nothing about permissions required, whether the operation blocks or is async, whether names must be unique, quota or cost implications, or whether the snapshot can be deleted later.

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?

A single front-loaded sentence with no filler; the only mild redundancy is 'persistent point-in-time storage snapshot', where the qualifiers overlap slightly. Nothing is wasted and the core action leads.

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

Completeness2/5

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

For a mutation tool with zero annotation coverage and no output schema, the description should at minimum say what the call returns (e.g., a snapshot ID) and any side effects or follow-up steps. As written, an agent knows what the tool does but not what to expect from invoking it.

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%, so all three parameters are already documented, and the description's mention of a 'database cluster branch' reinforces the branch_id semantics and the 'persistent' nature of the name label. It adds mild framing but no new syntax or constraint details beyond the schema.

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

Purpose4/5

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

States a specific verb and resource: 'Create a persistent point-in-time storage snapshot of a database cluster branch.' This clearly separates it from read-only siblings like mnemon_list_snapshots, mnemon_pitr_restore, or mnemon_time_travel, though it does not name any alternative explicitly.

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

Usage Guidelines3/5

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

Usage is only implied by the verb 'Create' – an agent can infer it is the write-path counterpart to listing or restoring snapshots. There is no explicit guidance on when to take a snapshot versus branching, cloning, or using PITR, and no preconditions are stated.

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