Folklore Clinical Variant Interpretation MCP

Find live literature for a resolved public gene

search_gene_literature

Read-onlyIdempotent

Retrieve a live publication capture for a resolved gene_id and snapshot_id. Returns source links, match labels, capture time/hash, degradation and gene/snapshot/sort-bound cursors. This capture is separate from the immutable reference snapshot and contains no abstracts.

Input Schema

Name	Required	Description	Default
`sort`	No	Discovery ordering. Keep the same sort for continuation pages.	relevance
`limit`	No	Maximum publication records in one live discovery page, from 1 to 25.
`cursor`	No	Opaque next_cursor returned for this same gene, snapshot and sort. Omit for the first page.
`gene_id`	Yes	Canonical HGNC gene_id returned by resolve_gene. Select an explicit candidate when resolution is ambiguous.
`snapshot_id`	Yes	identity_snapshot_id returned by resolve_gene, or snapshot_id from the current gene profile. Restart resolution after snapshot_unavailable.

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.

Changed3 schema fields changedOct 31, 2026

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

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds genuine behavioral context on top: the result is a live capture that may be degraded, it carries capture time/hash and match labels, cursors are bound to gene/snapshot/sort, and abstracts are absent. 'Contains no abstracts' is a return-value detail that partially duplicates the output schema, keeping it from a 5.

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?

Three tight sentences, front-loaded with the operation and inputs before the payoff and the snapshot caveat. Dense but nothing is wasted; the only redundancy is restating return fields that the output schema already covers.

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 an output schema present, the description need not enumerate return values, and it still adds the key caveat that this is a live, possibly degraded capture distinct from the immutable snapshot. Parameter coverage is complete, so an agent has everything needed to invoke it correctly; only explicit sibling routing is missing.

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%, so every parameter is already documented, establishing a baseline of 3. The description reinforces the cursor contract ('gene/snapshot/sort-bound cursors') but adds no syntax, defaults, or limits beyond what the schema already states for sort, limit, and cursor.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb and resource — 'Retrieve a live publication capture for a resolved gene_id and snapshot_id' — so an agent knows exactly what is being fetched and what the two key inputs are. It also draws a line between the live capture and the immutable reference snapshot, which hints at the sibling corpus tools, though it never names them outright.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: the tool is only callable with a resolved gene_id and snapshot_id from resolve_gene, which the schema reinforces, so the prerequisite chain is discoverable. However, the description never explicitly says when to prefer this over search_literature_corpus, search_variant_literature, or get_publication_details, leaving the agent to infer routing from the 'live capture vs immutable snapshot' remark.

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.