Skip to main content
Glama
PeWu

WikiTree MCP server

by PeWu

get_ancestors

Retrieve ancestor information from WikiTree by specifying a person ID and generation depth to explore family lineage and relationships.

Instructions

Retrieve ancestors for a given person ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyYesWikiTree ID
depthNoNumber of generations to retrieve
bioFormatNo
fieldsNo
resolveRedirectNo

Implementation Reference

  • The handler for the "get_ancestors" tool, which extracts arguments from the request and calls the wikitree library's getAncestors function.
    case "get_ancestors": {
      const { key, depth, bioFormat, fields, resolveRedirect } = args as any;
      const ancestors = await wikitree.getAncestors(key, { depth, bioFormat, fields, resolveRedirect }, options);
      return { content: [{ type: "text", text: JSON.stringify(ancestors, null, 2) }] };
    }
  • Registration and input schema definition for the "get_ancestors" tool.
      name: "get_ancestors",
      description: "Retrieve ancestors for a given person ID",
      inputSchema: {
        type: "object",
        properties: {
          key: { type: "string", description: "WikiTree ID" },
          depth: { type: "number", description: "Number of generations to retrieve" },
          bioFormat: { type: "string", enum: ["wiki", "html", "both"] },
          fields: { type: "array", items: { type: "string" } },
          resolveRedirect: { type: "boolean" },
        },
        required: ["key"],
      },
    },
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions retrieval but lacks details on permissions, rate limits, error handling, or output format. For a tool with 5 parameters and no output schema, this leaves significant behavioral gaps.

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, direct sentence with zero wasted words, making it highly concise and front-loaded. It efficiently conveys the core purpose without unnecessary elaboration.

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 tool's complexity (5 parameters, no annotations, no output schema), the description is inadequate. It doesn't explain return values, behavioral traits, or parameter usage, leaving the agent with insufficient context to use the tool effectively beyond basic purpose.

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 40%, with only 'key' and 'depth' described in the schema. The description adds no parameter semantics beyond implying 'person ID' relates to 'key', failing to compensate for the coverage gap or explain parameters like 'bioFormat', 'fields', or 'resolveRedirect'.

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 action ('Retrieve') and target ('ancestors for a given person ID'), making the purpose understandable. However, it doesn't differentiate from sibling tools like 'get_descendants' or 'get_relatives' which likely retrieve similar family data, missing explicit sibling distinction.

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?

The description provides no guidance on when to use this tool versus alternatives like 'get_descendants' or 'get_relatives', nor does it mention prerequisites or context for usage. It merely states what the tool does without indicating appropriate scenarios.

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