Skip to main content
Glama

search_variants

Filter variants by genomic region, allele frequency, and missing data thresholds, then export variant metadata to a CSV file.

Instructions

Search variants matching filters server-side and write the matching list to CSV.

Same filters as count_variants (region / MAF / missing-data). Returns variant metadata only (id, chrom, pos, ref, alt) — no genotypes are fetched — and writes variant_search.csv. Use count_variants first to size the result; max_variants caps how many are retrieved. For downstream genotype analysis on a filtered subset, use the region/min_maf options on the QC/diversity tools instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
endNoRegion end position, 1-based inclusive.
startNoRegion start position, 1-based inclusive.
max_mafNoMaximum minor-allele frequency (0-1).
min_mafNoMinimum minor-allele frequency (0-1).
output_dirNoDirectory for the output CSV(s) (default ./gigwa_results/<module>/).
max_variantsNoMaximum number of matching variants to retrieve.
reference_nameNoChromosome/contig name to restrict the search to (see list_sequences).
max_missing_dataNoMaximum per-variant missing-data fraction (0-1).
variant_set_db_idYesBrAPI variantSetDbId identifying the run (MODULE§project§run); from list_variant_sets / list_content.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

No annotations provided, so description must disclose behavior. It states writes variant_search.csv, returns only metadata (id, chrom, pos, ref, alt), no genotypes, and max_variants limit. Could mention overwrite behavior, but overall transparent.

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?

Description is concise with two sentences and clear bullet points. Front-loaded with purpose. Slightly informal structure but no wasted words.

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

Completeness4/5

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

Given 9 parameters and multiple siblings, the description covers purpose, filter similarities, output format, result cap, and alternative tools. Output schema exists but description adequately explains return values.

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% (all 9 parameters described in schema). Description adds minimal value by grouping filters as 'Same filters as count_variants', but does not enhance individual parameter meaning beyond schema.

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 clearly states the tool searches variants server-side and writes results to CSV, specifying the filter types and output filename. It distinguishes from siblings by referencing count_variants and QC/diversity tools.

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?

Explicitly recommends using count_variants first to size results, notes max_variants cap, and suggests alternatives for downstream genotype analysis (region/min_maf options on QC/diversity tools).

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

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