Skip to main content
Glama
oliverhruby

Gramps MCP

by oliverhruby
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

manage_event

Create, read, update, or delete event records in Gramps Web genealogy data. Manage event details like dates, places, and citations directly through the API.

Instructions

Create, read, update or delete Gramps Event records. Writes: create, update, delete.

action=get lists events (handle empty) or returns one event by handle. action=create posts a full Event JSON object in data; action=update PUTs data to /events/; action=delete removes it. Event payload fields: gramps_id, type, date, description, place, citations, notes, attribute_list, media_list, change, ... . Events are typically referenced by Person/Family event_ref_list entries.

Args: action: The operation, "get", "create", "update" or "delete". handle: Event handle; required for get-one, update, delete. data: The Event object for create/update (required for those). query: Optional dict of extra query-string parameters for reads. instance: Gramps Web base URL from get_instances; default = first.

Returns: dict: {"status", "url", "data"}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataNo
queryNo
actionYes
handleNo
instanceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It covers the actions, parameters, and return format, but does not mention side effects, permissions, reversibility, or error handling. Adequate for a CRUD tool, but not rich.

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 description is well-structured with sections for actions, parameters, and returns. It is concise enough to scan, though the example field list could be trimmed. Front-loaded purpose is clear.

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?

Given 5 parameters, nested objects, no output schema, and no annotations, the description covers the essential operational aspects: actions, parameter semantics, return shape, and a note on typical usage context. It lacks error handling or edge-case details, but is largely complete for an agent to invoke correctly.

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. It explains every parameter: action options, handle requirement for get-one/update/delete, data structure with example fields, query for read parameters, and instance sourcing. This far exceeds the schema's bare property names.

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 explicitly states 'Create, read, update or delete Gramps Event records', using a specific verb and resource. It clearly distinguishes this from sibling tools (e.g., manage_person, manage_family) by focusing on Event records, and enumerates the four CRUD actions.

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 provides useful context (e.g., events are referenced by Person/Family event_ref_list entries) and notes the instance default from get_instances. It does not explicitly contrast with sibling tools, but the event-specific scope makes the intended usage clear.

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