Skip to main content
Glama
PeWu

WikiTree MCP server

by PeWu

call_api

Directly access WikiTree's genealogical data API to retrieve family relationships, biographies, and ancestor information through customizable API calls.

Instructions

Call any WikiTree API endpoint directly

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesWikiTree API action (e.g., 'searchPerson')
paramsNoParameters for the action

Implementation Reference

  • The handler for the 'call_api' tool, which uses 'wikitree.wikiTreeGet' to execute the request.
    case "call_api": {
      const { action, params } = args as any;
      const result = await wikitree.wikiTreeGet({ action, ...params }, options);
      return { content: [{ type: "text", text: JSON.stringify(result, null, 2) }] };
    }
  • The schema definition for the 'call_api' tool, specifying 'action' and 'params' as inputs.
    {
      name: "call_api",
      description: "Call any WikiTree API endpoint directly",
      inputSchema: {
        type: "object",
        properties: {
          action: { type: "string", description: "WikiTree API action (e.g., 'searchPerson')" },
          params: { type: "object", description: "Parameters for the action", additionalProperties: true },
        },
        required: ["action"],
      },
    },
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 states the tool calls API endpoints 'directly' but doesn't explain authentication requirements, rate limits, error handling, or what 'directly' implies (e.g., raw HTTP calls, response format). This is a significant gap for a generic API tool with potential side effects.

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 for the tool's purpose, making it easy for an agent 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 of a generic API tool with no annotations and no output schema, the description is incomplete. It lacks details on authentication, error responses, rate limits, and how to interpret results, which are critical for correct invocation. The presence of sibling tools adds context but isn't addressed.

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?

Schema description coverage is 100%, so the schema already documents both parameters (action and params). The description adds no additional meaning beyond what the schema provides (e.g., examples of actions, structure of params). Baseline 3 is appropriate as the schema does the heavy lifting.

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 tool's purpose: 'Call any WikiTree API endpoint directly' specifies the verb ('call') and resource ('WikiTree API endpoint'). It distinguishes from siblings like 'get_person' by being a generic API caller rather than a specific data retrieval function. However, it doesn't specify what 'directly' means operationally, keeping it from 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?

The description provides no guidance on when to use this tool versus the sibling tools (get_ancestors, get_descendants, get_person, get_relatives). It doesn't mention alternatives, prerequisites, or exclusions, leaving the agent to infer usage based on the generic nature of the tool versus specialized siblings.

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