Skip to main content
Glama

import_dartseq

Convert DArTseq SNP or Silico-DArT xlsx reports to VCF and import them into Gigwa, using accurate 2-row genotype calling so reference homozygotes are not mis-imported as heterozygous.

Instructions

Import DArTseq data from xlsx report(s) into Gigwa.

Converts the DArTseq SNP and/or Silico-DArT xlsx report(s) to a standard VCF — doing the 2-row genotype calling in Python (so reference homozygotes are not mis-imported as heterozygous, as Gigwa's built-in DArT parser does) — and uploads it to create/append a database (module), project and run.

Provide at least one of snp_xlsx / silico_xlsx (absolute paths). SNP and Silico use different allele models; importing both into the same run is unusual — prefer separate runs unless you specifically intend to combine them.

If reference_fasta is given (a reference genome FASTA or a prebuilt minimap2 .mmi index — an .mmi is loaded directly with no re-indexing, preferred for large genomes), the SNP markers' tag sequences are aligned to it and uniquely-mapped markers (mapq ≥ min_mapq) are imported genome-anchored (real chromosome/position); the rest stay on an Unmapped contig. Without it, all markers go on Unmapped.

positions_csv reuses a mapping already produced by map_dartseq_to_reference (its dartseq_positions.csv) instead of re-aligning — much faster when you've already inspected the mapping. Provide either reference_fasta or positions_csv, not both.

Set clear_project_data=True to replace any existing data in the project, skip_monomorphic=True to drop non-variant markers, and wait=False to return immediately with a progress token instead of blocking until done.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
runYesTarget run name within the project.
waitNoBlock until the job finishes (True, default) or return immediately once it's kicked off (False) -- an import returns a progress token to poll with get_import_progress, an export returns a download URL to poll with get_export_progress and retrieve with fetch_export_file.
moduleYesTarget Gigwa database (module) name.
ploidyNoSample ploidy (default 2).
projectYesTarget project name within the database.
min_mapqNoMinimum mapping quality for a tag to count as uniquely mapped.
snp_xlsxNoPath to a DArTseq SNP xlsx report.
technologyNoFree-text genotyping technology label (e.g. 'DArTseq', 'WGS', 'GBS').DArTseq
silico_xlsxNoPath to a Silico-DArT xlsx report.
positions_csvNoPath to a dartseq_positions.csv (from map_dartseq_to_reference) to reuse instead of re-aligning.
reference_fastaNoPath to a reference genome FASTA or a prebuilt minimap2 .mmi index, for genome-anchoring.
skip_monomorphicNoDrop non-variant (monomorphic) markers during import.
clear_project_dataNoReplace any existing data in the project before importing.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changedv1.9.1
    • changedInput schema / properties / wait / description
      Previous value: -"Block until the import finishes (True) or return a progress token immediately (False)."New value: +"Block until the job finishes (True, default) or return immediately once it's kicked off (False) -- an import returns a progress token to poll with get_import_progress, an export returns a download URL to poll with get_export_progress and retrieve with fetch_export_file."
  2. First observedv1.4.16

TDQS

A5/5.0
Behavior5/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 and meets it thoroughly. It reveals the custom 2-row genotype calling, the fact that unanchored markers go on an 'Unmapped' contig, that positions_csv skips re-alignment, that clear_project_data replaces existing data, and that wait=False returns a progress token.

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 long but tightly organized into logical paragraphs: overview, input requirements, mapping options, and flag effects. Every sentence adds operational detail, and the most important action and constraints are front-loaded before the detailed options.

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

Completeness5/5

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

For a complex 13-parameter import tool with no annotations and an output schema, the description covers every parameter and all major workflow branches: SNP-only, Silico-only, combined, genome-anchored, reused mapping, and async execution. It gives an agent enough context to select parameters correctly and anticipate side effects.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Although the schema already documents all 13 parameters, the description adds crucial semantics beyond the schema: absolute path requirement, the at-least-one constraint between snp_xlsx and silico_xlsx, mutual exclusivity of reference_fasta and positions_csv, .mmi being loaded directly without re-indexing, and the destructive effect of clear_project_data.

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?

The description opens with a specific action: 'Import DArTseq data from xlsx report(s) into Gigwa', naming the resource format, input, and destination. It further clarifies the conversion to VCF and the creation of database/project/run, which clearly distinguishes it from sibling tools like import_vcf and import_metadata.

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

Usage Guidelines5/5

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

The description gives explicit usage conditions: 'Provide at least one of snp_xlsx / silico_xlsx', 'prefer separate runs' when importing both types, and 'Provide either reference_fasta or positions_csv, not both'. It also references map_dartseq_to_reference as the source of positions_csv, giving the agent an actionable decision path among related tools.

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

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/gkanogiannis/Gigwa-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server