Skip to main content
Glama
DataCraftsmanAU

DataCraftsmanAU/vineverse-mcp

Get a person's family and line of descent

get_family
Read-onlyIdempotent

Retrieve parents, children, siblings, and spouses for any person, plus generation-by-generation ancestors and descendants. Correctly inverts parent-of relations to build the true family tree.

Instructions

Parents, children, siblings and spouses for any person, and with generations above 1 the line of descent — ancestors and descendants gathered one generation at a time. This is the tool for a genealogy, lineage or ancestry question: "who were Boaz's ancestors", "trace David's line", "who did Ruth marry".

Use this rather than reading relations off get_entity. The corpus contains no child-of edge at all — parentage is recorded only on the parent's document — so a person's own parent-of relations are their CHILDREN, and reading them as parents inverts the family tree. This tool does the inversion.

Called family rather than genealogy because it returns kinship as well as descent, and because two other things here own that word. The 680 ancestor-of edges assert descent across an unknown number of generations, so they cannot be composed into a generation-by-generation tree and are excluded from this one — read them off get_entity if you want them. And the genealogy PASSAGES — Genesis 5 and 10, Ruth 4, Matthew 1, Luke 3 — are indexed as a theme at themes/genealogy.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesPerson path, e.g. "people/moses"
generationsNoAbove 1, also returns ancestors and descendants generation by generation.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
noteNo
errorNo
personNo
licenceNo
parentsNo
spousesNo
childrenNo
siblingsNo
ancestorsNo
descendantsNo
Behavior5/5

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

Annotations already declare readOnlyHint and idempotentHint, so safety is covered. The description adds essential behavioral context: the corpus has no child-of edge, this tool performs the inversion, ancestor-of edges cannot be composed into a generation tree, and genealogy passages are a separate theme. This goes well beyond the annotations.

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 main functionality is front-loaded in the first sentence with examples, and the exclusions/alternatives follow. The later naming-rationale explanation is longer than strictly necessary, but every sentence either routes behavior, gives data-model warnings, or clarifies scope. It is appropriately sized for a complex tool with data-model pitfalls.

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 tool with complex lineage semantics, the description covers all needed topics: the precise result (parents/children/siblings/spouses), how generations expands the result, the crucial data-model inversion, excluded relation types, and alternative access points. Given the output schema exists and parameter schemas are complete, nothing important is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, both parameters have descriptions, so baseline is 3. The description adds a concrete path example, clarifies which parameters affect lineage depth, and states that generations are gathered one generation at a time, which briefly specializes meaning beyond the schema's one-sentence parameter descriptions.

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 has a specific verb + resource: it returns parents, children, siblings, and spouses for a person, and with generations above 1 a generation-by-generation line of descent. It uses concrete example queries like 'who were Boaz's ancestors' and explicitly distinguishes itself from get_entity, so the agent can tell it apart from siblings.

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?

It explicitly says 'Use this rather than reading relations off get_entity' and explains why parentage is recorded only on the parent's document. It also tells the agent that ancestor-of edges and genealogy passages should be obtained elsewhere (get_entity, themes/genealogy), so both inclusion and exclusion criteria are spelled out.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/DataCraftsmanAU/vineverse-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server