Skip to main content
Glama
Sign In
gnomancer

gnomancer

by codebase
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

family

Compares relatives’ raw DNA files to estimate shared DNA and relationships, trace maternal and paternal lines, compare panel genotypes, and check parent-parent-child allele inheritance locally.

Instructions

Compare two or more relatives' raw DNA files: shared DNA per pair with a relationship estimate, shared maternal/ paternal lines, side-by-side panel genotypes and, for parent-parent-child sets, which parent each allele came from plus a Mendelian-consistency check. Runs locally. Returns the pair table and report paths.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "paths": "<paths>"
    },
    "name": "family"
  }
}

Input Schema

NameRequiredDescriptionDefault
namesNo
pathsYes
out_dirNo
haplogroupsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.1

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden. It does usefully disclose that the tool 'runs locally' and returns report paths, but it omits what files get written to disk (and whether out_dir is created or overwritten), what happens with insufficient shared SNPs or mismatched kits, expected input file formats, and runtime/memory expectations for multi-genome comparisons.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two dense sentences that front-load the core comparison and then enumerate outputs; no filler. Slightly list-like but every clause carries information, and the computational-locality note is well placed at the end.

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?

This is a multi-file, file-writing analytical tool with no output schema, no annotations, and 0% parameter description coverage. The description should at minimum explain the 'names' and 'haplogroups' parameters, the input file format expectations, and what gets written where; as written it leaves an agent unable to invoke it correctly beyond guessing.

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 0% and there are four parameters. The description obliquely covers 'paths' ('raw DNA files') and 'out_dir' ('report paths'), but 'names' (per-file labels?) and 'haplogroups' (a boolean defaulting to true) are never explained in either schema or description, leaving half the interface opaque.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Compare') and a specific resource ('raw DNA files' of two or more relatives), then enumerates the concrete outputs: shared DNA per pair with relationship estimate, shared maternal/paternal lines, side-by-side panel genotypes, and parent-of-origin phasing for trios. This is clearly distinct from siblings like lookup, analyze, summary, and section.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Uses the phrase 'for parent-parent-child sets' to scope the phasing/Mendelian feature to a particular family structure, which implies when the extra output applies, but it never states prerequisites (minimum number of files, overlapping-SNP requirements) or explicitly contrasts with sibling tools such as analyze or summary.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools