Skip to main content
Glama
Sign In
gramps-evidence-mcp

gramps-evidence-mcp

by ianderso
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

export_backup

Create a full-tree backup export to disk before bulk writes, enabling recovery if a bulk operation fails.

Instructions

Write a full-tree export to disk. Take one before any bulk write.

Cheap insurance: a few seconds and one file. A bulk write that goes wrong cannot always be undone transaction by transaction; a dump can be re-imported.

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_backup"
  }
}

Input Schema

NameRequiredDescriptionDefault
dest_pathNoA new file in an existing directory; an existing file is never replaced. Omit for a timestamped file in the cache directory.
export_formatNo'gramps' (Gramps XML, lossless -- use this for a safety dump), 'ged', 'json', or 'csv'.gramps

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Adds meaningful context beyond annotations: explains the rationale (irreversibility of bulk writes), reassures on cost ('a few seconds and one file'), and clarifies recoverability ('can be re-imported'). The annotations already cover safety signals. Minor gap: doesn't mention disk space or overwrite behavior, though the schema covers the latter.

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?

Two short paragraphs, front-loaded with the core action, then rationale. Every sentence earns its place; no filler.

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 backup tool with no output schema, the description explains purpose, timing, cost, and recovery value. It doesn't explain what the export returns (file path?), but that's not critical for an agent invoking it. Complete enough.

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 coverage is 100%, so parameters are thoroughly documented in the schema itself ('gramps' as lossless safety dump, dest_path behavior). The description adds no parameter-specific detail, which is acceptable given full schema coverage. Baseline 3 is appropriate.

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 clear verb+resource ('Write a full-tree export to disk'), which distinguishes it from read-only siblings like query_objects or get_object. It doesn't name a sibling alternative, but its purpose is unmistakable.

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

Usage Guidelines4/5

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

Gives clear timing guidance ('Take one before any bulk write'), which is a concrete usage condition. It lacks explicit when-not-to-use guidance, but the context is well-defined for a backup tool.

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