Skip to main content
Glama

manage_user

Create, update, delete, list, or fetch Gramps Web users and change their passwords via the Gramps API. Handles user administration with role, email, and tree data.

Instructions

Administer Gramps Web users. Writes: create, update, delete, change_password.

action=list lists users (GET /users/); action=get returns one user by name; action=create POSTs data (full_name, email, password, role and tree required by the API) to /users/; action=update PUTs data (role, email, full_name, name_new, tree) to /users//; action=delete removes the user; action=change_password POSTs with data = {"old_password", "new_password"}. Requires owner/admin permissions upstream for most actions.

Args: action: "list", "get", "create", "update", "delete" or "change_password". user_name: The user's name; required for get/update/delete/change_password. data: Body dict; required for create/update/change_password. instance: Gramps Web base URL from get_instances; default = first.

Returns: dict: {"status", "url", "data": user list/object or empty}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataNo
actionYes
instanceNo
user_nameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden, and it does so well: it states that create/update/delete/change_password write data, exposes the underlying HTTP verbs (GET, POST, PUT), notes the permission requirement, and defines the return dict. The only residual ambiguity is 'most actions' for permissions, which does not specify which actions are exempt.

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 front-loaded with a one-line purpose and write warning, then uses a structured action list, Args block, and Returns block. Everything present earns its place, and the detailed endpoint mapping is organized rather than verbose.

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 multi-action admin tool with a nested data object and no output schema, yet the description covers operations, required fields, permissions, endpoints, instance selection, and return shape. An agent has enough context to select and invoke each action without needing to inspect the API.

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%, but the description fully compensates: it enumerates valid action values, states when user_name is required, specifies data fields per API call, and documents the instance default. This is far more actionable than the bare JSON Schema with only titles and defaults.

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 the specific verb-resource pair 'Administer Gramps Web users' and then enumerates six concrete actions (list, get, create, update, delete, change_password). This clearly distinguishes it from sibling manage_* tools because the resource is users and the action set is explicit.

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 action-by-action breakdown tells an agent exactly which parameters are needed for each operation, and 'instance: Gramps Web base URL from get_instances' explicitly routes to a sibling tool. It lacks an explicit 'use X instead for non-user administration' statement, but the naming and content make the tool's domain unambiguous.

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