Skip to main content
Glama
Sign In
gramps-evidence-mcp

gramps-evidence-mcp

by ianderso
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

get_ancestors

Read-only

Trace a person's ancestors up to a chosen number of generations, returning a nested parents tree. Living or private ancestors are redacted unless include_private is enabled.

Instructions

Walk a person's ancestors up to N generations (a nested parents tree).

Living/private ancestors appear as redacted stubs unless include_private is set.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "person": "<person>"
    },
    "name": "get_ancestors"
  }
}

Input Schema

NameRequiredDescriptionDefault
personYesRoot person handle or gramps_id.
generationsNoHow many generations up.
include_privateNoShow living people and private records in full. Only when the user asks for them; they are withheld by default.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations cover the safety profile (readOnlyHint=true, openWorldHint=false), and the description adds genuinely non-obvious behavior: living/private ancestors are returned as redacted stubs by default. It also discloses the nested-tree return shape, which matters since there is no output schema. It stops short of describing error behavior for an unknown person.

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?

Two sentences, no filler. The core operation is front-loaded and the privacy caveat is placed second, where it belongs.

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?

With no output schema, the description usefully sketches the return shape (nested parents tree with redacted stubs) and the annotations carry the safety profile. It is nearly complete; only failure modes and depth-limit behavior are left unaddressed.

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 all three parameters (person, generations, include_private) are already documented with types, defaults, and bounds. The description echoes 'up to N generations' and the include_private effect with no additional syntax or format detail, so the baseline 3 applies.

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 ('Walk') and resource ('ancestors') with scope ('up to N generations') and return shape ('a nested parents tree'). An agent can distinguish it from the sibling get_descendants purely on the description.

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

Usage Guidelines3/5

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

The description implies when to use it (tracing ancestry upward) and hints at the privacy trade-off, but never explicitly names alternatives such as get_person or get_descendants, nor states exclusions. Usage is inferable rather than stated.

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