Pedigree MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_pedigree_documentationA | Returns comprehensive documentation for the pedigree data format. ALWAYS call this first before generating a pedigree to understand the required data structure, properties, and examples. |
| generate_pedigreeA | Generates a pedigree tree (Bennett 2008 standard) in PNG or SVG format. IMPORTANT: Use mother/father for ALL individuals with known parents - siblings share same parents. Only use top_level:true for founders with NO known parents. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have completely distinct purposes: one generates a pedigree tree in visual formats, while the other provides documentation about the data format. There is no overlap in functionality, making it impossible for an agent to confuse them.
Both tools follow a consistent verb_noun naming pattern (generate_pedigree, get_pedigree_documentation) with clear, descriptive names that align well with their functions. There are no deviations or mixed conventions.
With only two tools, the server feels under-scoped for a pedigree domain, which typically involves more operations like data validation, editing, or querying. While the tools cover core tasks, the count is too low for comprehensive coverage.
The server lacks essential operations for a pedigree system, such as creating, updating, or deleting pedigree data, validating input, or querying specific individuals. The tools only handle generation and documentation, leaving significant gaps that will likely cause agent failures in real-world workflows.