Skip to main content
Glama
musharna

plant-genomics-mcp

by musharna

Known Variants

locus_variants
Read-onlyIdempotent

List natural germline variants overlapping a plant locus, returning SNPs and indels with IDs, consequence, alleles, and clinical significance via Ensembl.

Instructions

List natural (germline) variants overlapping a locus's genomic span via Ensembl (rest.ensembl.org; free, no key). Resolves the locus → gene coordinates, then returns EVA/dbSNP-sourced SNPs and indels with id, source, consequence class, alleles, and clinical significance. variant_count is the true overlap total; the variant list is capped for payload size with truncated flagged. Opens the variation axis (distinct from get_sequence / ensembl_region_query). Works for all 12 organisms. Defaults to arabidopsis_thaliana; pass organism= for other species.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax variant rows to return. 'variant_count' always reports the true pre-cap total and 'truncated' says whether the cap bit.
locusYese.g. AT1G01010 (Arabidopsis), Os01g0100100 (rice RAP-DB)
organismNoPlant organism — accepts canonical slug (arabidopsis_thaliana), scientific or common name, or NCBI taxidarabidopsis_thaliana

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
locusYes
regionYesQueried gene span, e.g. '1:33666-37840'
gene_endNoGene span end (1-based)
organismYesResolved Ensembl species slug
variantsNoPer-variant {id, source, consequence_type, alleles, …}
truncatedYesTrue if the variant list was capped
gene_startNoGene span start (1-based)
variant_countYesTotal overlapping variants (pre-cap)
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false. The description adds valuable context: it explains the data source, the resolution process (locus to gene coordinates), the variant_count vs capped list behavior, and the 'truncated' flag. No contradictions.

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?

Two sentences, front-loaded with core purpose, immediately followed by essential details. No filler; every clause adds value.

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?

Despite the tool's moderate complexity (3 parameters, external API, multiple organisms, output cap), the description covers all essential aspects: source, data content, organism support, cap behavior, and sibling differentiation. Output schema exists, so return values need not be elaborated.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3. The description adds meaning beyond schema by providing examples for locus (AT1G01010), clarifying organism parameter accepted formats (slug, name, taxid), and explaining the limit parameter's cap and truncation reporting.

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 lists natural variants overlapping a locus's genomic span, specifying the source (Ensembl via EVA/dbSNP), the data fields returned, and explicitly distinguishes it from sibling tools (get_sequence, ensembl_region_query). The verb 'list' and resource 'variants' are specific.

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

Usage Guidelines4/5

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

The description provides clear context for when to use the tool (to retrieve germline variants) and explicitly names two alternatives it is distinct from. However, it does not elaborate on when not to use it or list other possible alternatives among the many sibling 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/musharna/plant-genomics-mcp'

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