Skip to main content
Glama
PeWu

WikiTree MCP server

by PeWu

get_person

Retrieve detailed genealogical records from WikiTree by providing a person's ID to access biographies and family relationship data.

Instructions

Retrieve a single person record from WikiTree

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyYesWikiTree ID (e.g., 'Smith-1')
bioFormatNoFormat of the biography
fieldsNoFields to retrieve
resolveRedirectNoWhether to resolve redirects

Implementation Reference

  • The handler implementation for the "get_person" tool, which parses the request arguments and calls the wikitree library's getPerson method.
    case "get_person": {
      const { key, bioFormat, fields, resolveRedirect } = args as any;
      const person = await wikitree.getPerson(key, { bioFormat, fields, resolveRedirect }, options);
      return { content: [{ type: "text", text: JSON.stringify(person, null, 2) }] };
    }
  • The tool registration schema for "get_person", defining the expected input parameters.
    {
      name: "get_person",
      description: "Retrieve a single person record from WikiTree",
      inputSchema: {
        type: "object",
        properties: {
          key: { type: "string", description: "WikiTree ID (e.g., 'Smith-1')" },
          bioFormat: { type: "string", enum: ["wiki", "html", "both"], description: "Format of the biography" },
          fields: { type: "array", items: { type: "string" }, description: "Fields to retrieve" },
          resolveRedirect: { type: "boolean", description: "Whether to resolve redirects" },
        },
        required: ["key"],
      },
    },
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. While 'Retrieve' implies a read-only operation, it doesn't clarify authentication requirements, rate limits, error handling, or what happens with invalid keys. For a tool with no annotation coverage, this leaves significant gaps in understanding its behavior.

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, clear sentence that efficiently communicates the core purpose without unnecessary words. It's appropriately sized for a simple retrieval tool and front-loads the essential information.

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

Completeness3/5

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

Given the tool's moderate complexity (4 parameters, no output schema, no annotations), the description is minimally adequate but incomplete. It covers the basic purpose but lacks behavioral details, usage context, and output expectations, which are important for a tool interacting with an external API like WikiTree.

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?

The description adds no parameter-specific information beyond what's already documented in the input schema (which has 100% coverage). It doesn't explain the significance of the 'key' parameter (e.g., that it's a unique identifier) or provide examples for 'fields' or 'bioFormat'. With high schema coverage, the baseline is 3.

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 resource ('a single person record from WikiTree'), making the purpose immediately understandable. However, it doesn't explicitly differentiate this tool from sibling tools like get_ancestors or get_descendants, which also retrieve person-related data but with different scopes.

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. It doesn't mention sibling tools like get_ancestors (for lineage) or get_relatives (for family connections), nor does it specify prerequisites or typical use cases for retrieving a single person record.

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