Skip to main content
Glama

manage_tree

Manage Gramps Web family trees with actions to list, inspect, create, update, enable or disable, repair, migrate, verify, and set configuration.

Instructions

Inspect or administer Gramps Web family trees. Writes: create, update, disable, enable, repair, migrate, verify, config_set.

action=list lists trees (GET /trees/); action=get inspects one tree (tree_id '-' means the current tree); action=create adds a tree (data = {"name": , "quota_media", "quota_people", "min_role_ai"}); action=update renames/rescales a tree; action=disable/action=enable toggle login for a tree; action=repair checks/repairs its database; action=migrate upgrades its schema; action=verify runs integrity checks; action=config_get/action=config_set read or write tree configuration. Admin-only upstream. Note: this API version has no tree delete endpoint (delete trees via the server CLI).

Args: action: "list", "get", "create", "update", "disable", "enable", "repair", "migrate", "verify", "config_get" or "config_set". tree_id: Tree id; required except for list/create; '-' = current tree. data: Body dict for create/update/config_set (create requires 'name'). instance: Gramps Web base URL from get_instances; default = first.

Returns: dict: {"status", "url", "data": tree details or configuration}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataNo
actionYes
tree_idNo
instanceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

With no annotations provided, the description fully carries the behavioral burden. It explicitly separates read actions from writes, explains what each action does (create, disable/enable, repair, migrate, verify, config_set), documents the missing delete endpoint, and states the admin-only requirement.

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?

The description is long but dense and well-structured: a one-line summary, action-by-action breakdown, parameter list, and return shape. It front-loads the core purpose and every section earns its place given the tool's 11 distinct actions and 4 parameters.

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?

This is a complex tool with no output schema and no annotations, yet the description covers action semantics, parameter constraints, permissions, an important deletion caveat, and the return structure. Nothing an agent needs to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate, and it does comprehensively. Each parameter is explained: action values are listed, tree_id semantics including '-' for current tree are given, data requirements include the required 'name' field for create, and instance is defined with a default and a reference to get_instances.

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?

The description opens with a specific verb and resource: 'Inspect or administer Gramps Web family trees.' It then enumerates every supported action, making it unambiguous what the tool does and clearly distinguishing it from sibling manage_* tools that target different Gramps resources.

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?

The description gives clear operational context: it lists all action modes, marks the tool as admin-only, and explicitly notes that deletion is not supported and should be done via the server CLI. It does not name a sibling tool to prefer for tree viewing, but the resource-specific scope is enough for an agent to select it correctly.

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