Skip to main content
Glama

Myvariant

by io.github.pipeworx-io

Query

query
Read-onlyIdempotent

Search aggregated human genetic-variant annotations on MyVariant.info. Accepts an rsID ("rs58991260"), an HGVS id ("chr1:g.218631822G>A"), or a fielded query ("dbnsfp.genename:CDK2", "clinvar.rcv.clinical_significance:pathogenic"). Each hit merges dbSNP, ClinVar clinical significance, CADD/dbNSFP deleteriousness scores, and gnomAD population allele frequencies. Returns { total, hits }; hit._id is usually the HGVS id you can pass to the variant tool.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sizeNoMax hits to return, 1-1000 (default 10).
queryYesrsID, HGVS id, or fielded query. e.g. "rs58991260", "chr1:g.218631822G>A", "dbnsfp.genename:CDK2".
fieldsNoComma-separated return fields (default: all). e.g. "dbsnp,clinvar,cadd.phred,gnomad_genome.af".

Schema Changelog

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

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "query": "rs58991260"
+  },
+  {
+    "fields": "dbsnp,clinvar,cadd.phred,gnomad_genome.af",
+    "query": "dbnsfp.genename:CDK2",
+    "size": 20
+  }
+]
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint. Description adds: merges dbSNP, ClinVar, CADD, gnomAD; returns { total, hits }; hit._id is HGVS id. No contradiction; adds substantial behavioral context.

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?

Three concise sentences: purpose, examples, return structure plus sibling cross-reference. No fluff, front-loaded with key info.

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?

No output schema, but description fully explains return format. Covers input types, merged data sources, and links to variant tool. Lacks error/edge-case info, but annotations cover safety. Very complete given complexity.

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 description need not repeat. Yet it adds examples for query parameter, mentions fields parameter's comma-separated format and default (all). This enriches understanding 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?

Starts with 'Search aggregated human genetic-variant annotations on MyVariant.info' – clear verb+resource. Distinguishes from siblings by domain and explicitly names the 'variant' tool. Examples of query types remove ambiguity.

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?

Provides concrete examples of valid queries (rsID, HGVS, fielded) and mentions the variant tool for hit._id. Does not explicitly exclude other tools, but domain specificity and sibling context make usage clear.

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

All Myvariant toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0
Disambiguation2/5

Several clusters have overlapping purposes: ask_pipeworx and ask_pipeworx_beta are explicitly identical, and the five prediction-market tools (bet_research, polymarket_edges, polymarket_arbitrage, polymarket_kalshi_spread, polymarket_fill_risk) all target 'find edge in Polymarket markets' with subtle differences. query and variant both retrieve the same variant annotations, and ai_visibility_check vs scan_competitor_ai_presence are near-duplicates.

Naming Consistency4/5

Most tools follow a consistent verb_noun or domain-prefixed pattern (ask_pipeworx, compare_entities, resolve_entity, polymarket_edges, remember/recall/forget). Minor deviations exist: the bare nouns query, variant, and metadata are less descriptive, and ask_pipeworx_beta uses a suffix instead of a clean verb pattern, but the overall convention is fairly uniform.

Tool Count2/5

34 tools is far too many for a server named 'Myvariant' whose stated domain is genetic variant annotations. The set is a grab-bag spanning genetic data, Pipeworx query routing, Polymarket betting, memory persistence, subscriptions, AI visibility, and npm dependency scanning. Most tools are unrelated to the server's apparent purpose, making the count feel bloated and incoherent.

Completeness3/5

Individual clusters are reasonably complete: variants have search/get/metadata, memory has remember/recall/forget, and subscriptions have subscribe/list/unsubscribe/alerts. However, as a Myvariant server the surface is massively over-scoped yet oddly missing any batch-variant or annotation-source-specific lookup, and the sprawling multi-domain design makes 'complete' hard to meaningfully assess.

Resources