Skip to main content
Glama
PeWu

WikiTree MCP server

by PeWu

get_relatives

Retrieve family relationships for WikiTree profiles to explore ancestors, descendants, spouses, and siblings using the WikiTree MCP server.

Instructions

Retrieve relatives for a given person ID or list of IDs

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keysYesWikiTree IDs
getParentsNo
getChildrenNo
getSpousesNo
getSiblingsNo
bioFormatNo
fieldsNo

Implementation Reference

  • The handler logic for the "get_relatives" tool, which calls `wikitree.getRelatives` with the provided arguments.
    case "get_relatives": {
      const { keys, getParents, getChildren, getSpouses, getSiblings, bioFormat, fields } = args as any;
      const relatives = await wikitree.getRelatives(keys, { getParents, getChildren, getSpouses, getSiblings, bioFormat, fields }, options);
      return { content: [{ type: "text", text: JSON.stringify(relatives, null, 2) }] };
    }
  • The registration and schema definition for the "get_relatives" tool.
      name: "get_relatives",
      description: "Retrieve relatives for a given person ID or list of IDs",
      inputSchema: {
        type: "object",
        properties: {
          keys: { type: "array", items: { type: "string" }, description: "WikiTree IDs" },
          getParents: { type: "boolean" },
          getChildren: { type: "boolean" },
          getSpouses: { type: "boolean" },
          getSiblings: { type: "boolean" },
          bioFormat: { type: "string", enum: ["wiki", "html", "both"] },
          fields: { type: "array", items: { type: "string" } },
        },
        required: ["keys"],
      },
    },
Behavior2/5

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

With no annotations, the description carries full burden but only states the basic action. It doesn't disclose behavioral traits such as permissions needed, rate limits, error handling, or what 'retrieve' entails (e.g., format, pagination). This is inadequate for a tool with 7 parameters and no output schema.

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?

The description is a single, efficient sentence with zero waste. It's front-loaded and appropriately sized, making it easy to parse without unnecessary details.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity (7 parameters, low schema coverage, no annotations, no output schema), the description is incomplete. It doesn't explain the tool's behavior, output format, or parameter meanings, leaving significant gaps for an AI agent to understand and invoke it correctly.

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

Parameters2/5

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

Schema description coverage is low at 14%, with only 'keys' parameter documented. The description adds minimal value by mentioning 'person ID or list of IDs', which loosely relates to 'keys', but doesn't explain the other 6 parameters (e.g., boolean flags for family types, 'bioFormat', 'fields'). It fails to compensate for the coverage gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb ('Retrieve') and resource ('relatives'), specifying it works for 'a given person ID or list of IDs'. It distinguishes from siblings like 'get_ancestors' and 'get_descendants' by focusing on immediate family relations, though it doesn't explicitly contrast them.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives like 'get_ancestors' or 'get_descendants' is provided. The description implies usage for retrieving relatives but lacks context on prerequisites, exclusions, or comparisons to sibling tools.

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/PeWu/wikitree-mcp'

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