Skip to main content
Glama
PeWu

WikiTree MCP server

by PeWu

get_descendants

Retrieve family tree descendants for a WikiTree person ID to explore genealogical relationships and access biography information across multiple generations.

Instructions

Retrieve descendants for a given person ID

Input Schema

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

Implementation Reference

  • The handler implementation for the 'get_descendants' MCP tool. It extracts arguments and calls the underlying `wikitree.getDescendants` library function.
    case "get_descendants": {
      const { key, depth, bioFormat, fields, resolveRedirect } = args as any;
      const descendants = await wikitree.getDescendants(key, { depth, bioFormat, fields, resolveRedirect }, options);
      return { content: [{ type: "text", text: JSON.stringify(descendants, null, 2) }] };
    }
  • Registration and input schema definition for the 'get_descendants' tool.
    {
      name: "get_descendants",
      description: "Retrieve descendants 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 doesn't cover aspects like rate limits, authentication needs, error handling, or what the output looks like (e.g., format, structure). This leaves significant gaps for a tool with 5 parameters.

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 no wasted words. It's front-loaded with the core purpose, making it easy to parse quickly.

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 (5 parameters, no annotations, no output schema), the description is incomplete. It lacks details on behavior, parameter usage, and output, leaving the agent with insufficient information to use the tool effectively beyond basic invocation.

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' having descriptions. The tool description adds no parameter details beyond the schema, failing to compensate for the coverage gap. For example, it doesn't explain what 'bioFormat' or 'fields' entail.

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 ('descendants for a given person ID'), making the purpose understandable. However, it doesn't explicitly differentiate from sibling tools like 'get_ancestors' or 'get_relatives', which would be needed for a perfect score.

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 is provided on when to use this tool versus alternatives like 'get_ancestors' or 'get_relatives'. The description only states what it does, without context about appropriate scenarios or exclusions.

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