Skip to main content
Glama
ianderso

gramps-evidence-mcp

by ianderso
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

add_place

Create a typed, parented place in a Gramps tree to prevent untyped duplicates that arise when event naming spawns places as a side effect.

Instructions

Create a place deliberately, with a type and a parent.

Use this instead of letting a place appear as a side effect of naming one in an event. That route produces an untyped, unparented place whose title is the bare string you typed, which is how duplicate hierarchies start.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
codeNoPostal or FIPS code.
nameYesThe place's own name, e.g. 'Cedar Flat'.
titleNoFull display title, e.g. 'Cedar Flat, Brannock, Ohio, USA'. Defaults to the name. This is what event place matching compares against, so set it properly.
parentNoHandle or gramps_id of an existing enclosing place. Must already exist — it is never created for you.
latitudeNoLatitude, decimal degrees.
longitudeNoLongitude, decimal degrees.
place_typeNoGramps place type: Town, City, County, State, Country, Parish, Farm, Building, and so on, or a custom type the tree already has.
allow_new_typeNoAccept a type that is neither a Gramps standard type nor one of the tree's custom types, creating it as a new custom type. Only when meant: a near-miss is refused with the closest names.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.2.0
    • addedInput schema / properties / allow_new_type
      Added value: +{
+  "default": false,
+  "description": "Accept a type that is neither a Gramps standard type nor one of the tree's custom types, creating it as a new custom type. Only when meant: a near-miss is refused with the closest names.",
+  "type": "boolean"
+}
    • changedInput schema / properties / place_type / description
      Previous value: -"Gramps place type: Town, City, County, State, Country, Parish, Cemetery, and so on."New value: +"Gramps place type: Town, City, County, State, Country, Parish, Farm, Building, and so on, or a custom type the tree already has."
  2. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare the mutation profile (readOnlyHint false, destructiveHint false, non-idempotent). The description adds real behavioral context: the deliberate route yields typed/parented places, while the implicit route produces duplicates. It stops short of noting that a repeated call is not idempotent and can itself create duplicate places, which would be the one remaining behavioral gap.

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?

Front-loaded with the core action in the first sentence, and the following sentences justify the 'deliberately' framing rather than padding it. Slightly more explanation of the anti-pattern than strictly needed, but every sentence carries information.

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 create tool with full schema coverage and no output schema, the description covers purpose, timing, and consequences well. The one missing piece is what the call returns (e.g., the new place's handle/gramps_id), which matters since no output schema exists to tell the agent.

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 description coverage is 100%, so baseline is 3. The description only echoes 'a type and a parent,' adding no syntax, format, or matching semantics beyond what the schema already documents for all eight parameters.

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?

States a specific verb and resource ('Create a place') with the distinguishing scope 'deliberately, with a type and a parent.' It also contrasts against the implicit side-effect route, so an agent can tell what this tool does differently from letting an event naming produce a place.

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?

Explicit when-to-use ('Use this instead of letting a place appear as a side effect of naming one in an event') with the failure consequence of the alternative ('untyped, unparented place... duplicate hierarchies'). Nothing is left to inference about when this tool is the right choice.

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