Skip to main content
Glama
alfonsoguv

DeepDNA MCP server

by alfonsoguv

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

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

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
read_dna_fileA

Read the user's raw DNA file (23andMe, AncestryDNA, MyHeritage or FamilyTreeDNA; .txt, .csv or .zip) on this computer and report, for each curated variant, one of four states: read, no_call, not_in_file, or unexpected_letters (the file's letters fit neither the record nor its complement). For positions the record marks as countable it gives how many copies of the variant allele the file shows, with the record's text and sources. Pass genes for what the user asked about (for example ["CYP2C19"] before discussing clopidogrel). APOE, BRCA1 and HFE are disease-risk genes: they are read only when named in genes, so do not offer or report them unless the user asks for them by name. A count at one position is not a metabolizer status, diplotype, diagnosis or dose: say so, and refer anything that could matter for health to a clinician and a validated test.

lookup_drug_geneA

Cited pharmacogenomic guidance for a gene, optionally for one drug, from DeepDNA's public API: the guideline (CPIC or DPWG where one exists, otherwise a drug label or the primary literature), a summary and sources. Sends only the gene and drug names. The phenotype groups it lists are the guideline's own: do not place the user in one from read_dna_file counts. Educational information, not a dose or a prescription.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.4/5.0

Scored across 2 tools

Disambiguation5/5

The two tools are cleanly separated: read_dna_file operates on a local DNA file and reports variant states, while lookup_drug_gene is a read-only query against a remote pharmacogenomic API. There is no plausible way to confuse one for the other, and each description reinforces the boundary.

Naming Consistency5/5

Both names follow the same verb_noun snake_case pattern (read_dna_file, lookup_drug_gene), with verbs drawn from the same read-verb family and concrete noun objects. No casing or convention drift.

Tool Count3/5

Two tools is on the thin side even for a narrowly scoped read-only domain, though each tool is substantive rather than trivial. A helper for listing curated genes/variants or mapping drugs to genes would round out the surface.

Completeness3/5

The core loop (read a DNA file, then fetch gene/drug guidance) is covered, but there is no way to enumerate which variants or genes the record curates, discover which drugs map to a gene, or search a record by rsID. Agents must already know the gene names to pass in, which is a notable gap.

Maintenance

ActivityMaintained
ResponsivenessUnresponsive