Skip to main content
Glama
mitomap-link
by berntpopp

Search MITOMAP Variants

search_variants
Read-onlyIdempotent

Find MITOMAP mtDNA variants by locus, disease text, status category, or rCRS position range; defaults to disease mutations, with options for polymorphisms.

Instructions

Search MITOMAP mtDNA variants by locus (MT-TL1, MT-ATP6, MT-CR...), disease text, MITOMAP status category and/or an rCRS position range. record_type defaults to disease_mutation (MITOMAP's coding/control and rRNA/tRNA mutation lists); use polymorphism or any for population polymorphisms. Unknown loci are rejected. Ordered by position, or by MITOMAP reference count with sort_by='reference_count' (most-published first); returns results with total/truncated/next_offset. Signature: search_variants(locus=, disease_query=, status=, record_type=, position_start=, position_end=, sort_by=, limit=, offset=, response_mode=).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_variants"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoPage size (1-100, default 20).
locusNoMITOMAP locus / MT- gene symbol (case-insensitive).
offsetNoRows to skip (default 0).
statusNoMITOMAP status category: reported, confirmed (Cfrm), conflicting_reports, unclear.
sort_byNoposition (default, rCRS order) or reference_count (most MITOMAP-cited first; ties by position).position
record_typeNodisease_mutation (default), polymorphism, or any.disease_mutation
position_endNorCRS position (1-16569), inclusive.
disease_queryNoCase-insensitive substring of MITOMAP's disease text, e.g. 'Leigh', 'LHON', 'MELAS'. Up to 5 alternatives (any matches) separated by '|', ' / ' or ' OR ': Leigh|NARP|MILS.
response_modeNoVerbosity: minimal (ids, locus, disease, status) | compact (default; + alleles, plasmy, GenBank counts, reference_count) | standard (get_variant: + up to 10 references with fenced titles; search_variants: + up to 10 PMIDs) | full (get_variant: + up to 50 references and every PMID; search_variants: + every PMID).compact
position_startNorCRS position (1-16569), inclusive.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.3

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the description's value is in adding error and result-shape behavior: unknown loci are rejected, results are ordered by position or by reference_count, and the response carries total/truncated/next_offset. It does not discuss rate limits or permissions, but for an open reference-database search that is a minor gap.

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

Conciseness3/5

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

Filter axes, defaults, and ordering are front-loaded and information-dense, which is good. However the final 'Signature: search_variants(...)' clause duplicates the input schema verbatim and adds no new information, and the single run-on paragraph buries distinct concerns (routing, validation, ordering, pagination) together.

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?

With 10 optional parameters and no output schema, the description does the essential work of describing the return envelope (total/truncated/next_offset) and per-mode verbosity via response_mode. Only the per-record field list is left to the schema enums, which is acceptable given how detailed that enum text is.

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 the baseline is 3; the description earns above baseline by explaining what disease_mutation actually contains (MITOMAP's coding/control and rRNA/tRNA mutation lists) and what 'most-published first' means for sort_by='reference_count'. The trailing signature line merely restates parameter names the schema already lists.

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 (search) and resource (MITOMAP mtDNA variants) and enumerates the four filter axes: locus, disease text, status category, position range. An agent can tell this is a bulk/filtered search rather than a single-record fetch, which separates it from the get_variant sibling named in the response_mode text.

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?

Gives concrete routing guidance for the most error-prone choice, 'record_type defaults to disease_mutation ...; use polymorphism or any for population polymorphisms', and warns that unknown loci are rejected. It stops short of stating explicitly when to prefer get_variant over this search, that routing must be inferred from the parameter prose.

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