Folklore Clinical Variant Interpretation MCP

Resolve a gene symbol, alias or stable identifier

resolve_gene

Read-onlyIdempotent

Resolve a human gene symbol, previous symbol, alias, HGNC, Ensembl or NCBI Gene identifier. Returns exact, alias, ambiguous, not_found or withdrawn status with candidates and identity_snapshot_id. Use a selected HGNC gene_id and snapshot_id with get_gene_profile. Gene-plus-HGVS and variant expressions use classify_germline_variant.

Input Schema

Name	Required	Description	Default
`query`	Yes	One public gene symbol, previous symbol, alias, HGNC ID, Ensembl gene ID or NCBI Gene ID.

Output Schema

Name	Required	Description	Default
`result`	Yes
`record_url`	Yes
`adapter_error`	Yes
`contract_version`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 31, 2026

changedInput schema / properties / query / description

Previous value: -"One public gene symbol, previous symbol, alias, HGNC ID, Ensembl gene ID or NCBI Gene ID. No patient or case narrative."New value: +"One public gene symbol, previous symbol, alias, HGNC ID, Ensembl gene ID or NCBI Gene ID."

changedOutput schema / properties / contract_version / const
```
Previous value: -"1"New value: +"2"
```

removedOutput schema / properties / usage_boundary

Removed value: -{
-  "additionalProperties": false,
-  "properties": {
-    "changes_variant_classification": {
-      "const": false
-    },
-    "intended_use": {
-      "const": "professional_gene_reference_review"
-    },
-    "not_for": {
-      "const": [
-        "patient_diagnosis",
-        "treatment_decision",
-        "variant_pathogenicity_classification"
-      ]
-    },
-    "patient_context_evaluated": {
-      "const": false
-    },
-    "review_required": {
-      "const": true
-    }
-  },
-  "required": [
-    "intended_use",
-    "patient_context_evaluated",
-    "review_required",
-    "changes_variant_classification",
-    "not_for"
-  ],
-  "type": "object"
-}

changedOutput schema / required

Previous value: -[
-  "contract_version",
-  "result",
-  "record_url",
-  "usage_boundary",
-  "adapter_error"
-]New value: +[
+  "contract_version",
+  "result",
+  "record_url",
+  "adapter_error"
+]

AddedOct 30, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the description's job is lighter. It adds real behavioral value by naming the five possible outcome statuses (exact, alias, ambiguous, not_found, withdrawn) and the returned candidates and identity_snapshot_id, telling the agent to expect non-exact resolutions rather than a boolean hit.

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 tight sentences: what it resolves, what it returns, where to go next. The disambiguation to classify_germline_variant is front-loaded at the end where it prevents the most likely misfire.

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 one-parameter resolution tool with full annotations and an output schema, nothing essential is missing: input space, outcome statuses, and the downstream handoff are all covered, and return-value structure is delegated to the output schema.

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?

With a single parameter at 100% schema coverage, the schema already documents the accepted identifier forms and length bounds. The description restates the identifier types but adds no format or syntax detail beyond what the schema provides, so the baseline 3 applies.

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 (resolve) and enumerates the exact input space: symbol, previous symbol, alias, HGNC, Ensembl or NCBI Gene ID, restricted to human genes. This is clearly distinguishable from siblings like get_gene_profile or classify_germline_variant at a glance.

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 routes the agent forward ('Use a selected HGNC gene_id and snapshot_id with get_gene_profile') and carves out an exclusion ('Gene-plus-HGVS and variant expressions use classify_germline_variant'). Both the when-to-use-next and the when-not-to-use-this cases are named.

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

All Folklore Clinical Variant Interpretation MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.