Folklore Clinical Variant Interpretation MCP

Read a page of gene records

get_gene_section

Read-onlyIdempotent

Read a gene-profile section using gene_id, snapshot_id and its returned opaque cursor. Returns source records, assembly/release, coverage, totals, count units and provenance. snapshot_unavailable requires a fresh resolution/profile request.

Input Schema

Name	Required	Description
`limit`	No	Maximum source records per page, from 1 to 50. Counts retain their original source unit.
`cursor`	No	Opaque next_cursor returned for this same gene, snapshot and section. Omit for its first page.
`gene_id`	Yes	Canonical HGNC gene_id returned by resolve_gene. Select an explicit candidate when resolution is ambiguous.
`section`	Yes	Source-qualified section from the current profile. Literature is a separate live capture; use search_gene_literature for it.
`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.8/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 safety profile is covered. The description adds real value beyond that: it names the pagination contract (opaque cursor), summarizes what a page yields (source records, assembly/release, coverage, totals, count units, provenance) and discloses a failure mode (snapshot_unavailable) with the remedy.

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?

Two tight sentences with the access keys front-loaded before the return payload and the error case. The return-value enumeration is slightly redundant given that an output schema exists, which keeps it just short of a 5.

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?

With annotations carrying the safety profile, a full output schema, and 100% parameter documentation, the description's remaining job is to explain the paging model and the snapshot_unavailable recovery, both of which it does. Nothing an agent needs in order to invoke it correctly 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 all five parameters, including the enum values and the cursor's same-gene/snapshot/section constraint, are already documented. The description only restates that the cursor is 'returned' and opaque, adding no new syntax or format detail, so the baseline of 3 applies.

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 definition names a specific verb and resource ('Read a gene-profile section') and enumerates the addressing keys (gene_id, snapshot_id, cursor), so its paginated-section-read purpose is unmistakable. It does not explicitly contrast itself with the sibling get_gene_profile, leaving the agent to infer that one is the full profile and this is a paged slice.

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 only implied: 'its returned opaque cursor' signals that follow-up pages go through this same tool, and 'snapshot_unavailable requires a fresh resolution/profile request' gives an error-recovery path. There is no explicit statement of when to choose this over get_gene_profile or which sibling to call first.

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.