Skip to main content
Glama

manage_place

Create, read, update, or delete Gramps Place records. Use filter queries for raw object data instead of full-text search.

Instructions

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

action=get lists places (handle empty) or returns one place by handle. action=create posts a full Place JSON object in data; action=update PUTs data to /places/; action=delete removes it. Place payload fields: gramps_id, name, type, longitude, latitude, alt_names, place_ref_list, enclosed_by, media_list, note_list, change, ... . Use manage_place with a filter query instead of search when you need raw object data rather than full-text hits.

Args: action: The operation, "get", "create", "update" or "delete". handle: Place handle; required for get-one, update, delete. data: The Place 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.7/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It explicitly discloses that this is a mutation tool, maps each action to an HTTP verb/endpoint, and states the return dict shape. It does not mention auth requirements, reversibility, or side effects of updates/deletes, but it provides substantially more behavioral context than the schema alone.

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-organized and front-loaded with the core purpose. It is slightly redundant: the opening sentence already says 'create, read, update or delete,' and the next sentence repeats the write subset. Overall the extra length is justified by the lack of annotations and output schema, but a small redundancy keeps it from being maximally concise.

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?

For a CRUD tool with five parameters, no annotations, and no output schema, this description is remarkably complete. It covers every parameter, the operation-specific behavior, the return structure, and the relationship to search. The open-ended Place object and query parameters would benefit from more examples, but the essential invocation context is fully present.

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 coverage is 0%, yet the description compensates thoroughly: it defines action values, explains when handle is required, identifies data as the Place object payload, clarifies query as read-only extra parameters, and states the instance default. It also lists common place payload fields, which the schema does not document at all.

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: 'Create, read, update or delete Gramps Place records.' It then maps each action to concrete behavior, making it unmistakable what the tool operates on. It also distinguishes itself from the search sibling by noting it returns raw object data rather than full-text hits.

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

Usage Guidelines5/5

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

The description explicitly says to use manage_place over search when raw object data is needed rather than full-text hits. It also explains the list-versus-single-read behavior based on whether handle is empty, giving an agent clear selection and invocation rules.

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