Folklore Clinical Variant Interpretation MCP

Get details for a PubMed publication

get_publication_details

Read-onlyIdempotent

Retrieve one PMID from the PubMed-derived genetics corpus, including title, abstract, authors, journal, publication types, MeSH terms, gene and variant mentions, retraction status and PubMed/PMC links.

Input Schema

Name	Required	Description	Default
`pmid`	Yes	One PubMed identifier to look up in Folklore's current corpus, as 1 to 12 digits without a PMID prefix.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedOct 31, 2026

removedOutput schema / additionalProperties
```
Removed value: -false
```

addedOutput schema / anyOf

Added value: +[
+  {
+    "additionalProperties": false,
+    "properties": {
+      "contract_version": {
+        "const": "2",
+        "title": "Contract Version",
+        "type": "string"
+      },
+      "publication": {
+        "$ref": "#/$defs/PublicPublicationDetails"
+      }
+    },
+    "required": [
+      "contract_version",
+      "publication"
+    ],
+    "title": "PublicationDetailsResponse",
+    "type": "object"
+  },
+  {
+    "additionalProperties": false,
+    "properties": {
+      "adapter_error": {
+        "anyOf": [
+          {
+            "additionalProperties": false,
+            "properties": {
+              "code": {
+                "minLength": 1,
+                "type": "string"
+              },
+              "message": {
+                "minLength": 1,
+                "type": "string"
+              },
+              "retryable": {
+                "type": "boolean"
+              }
+            },
+            "required": [
+              "code",
+              "message",
+              "retryable"
+            ],
+            "type": "object"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "contract_version": {
+        "const": "2",
+        "type": "string"
+      },
+      "record_url": {
+        "format": "uri",
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "result": {
+        "anyOf": [
+          {
+            "additionalProperties": true,
+            "properties": {
+              "search_contract_version": {
+                "const": "1.0",
+                "type": "string"
+              },
+              "status": {
+                "enum": [
+                  "resolved",
+                  "ambiguous",
+                  "not_found",
+                  "invalid_request",
+                  "unsupported",
+                  "resolution_unavailable"
+                ],
+                "type": "string"
+              }
+            },
+            "required": [
+              "search_contract_version",
+              "status"
+            ],
+            "type": "object"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      }
+    },
+    "required": [
+      "contract_version",
+      "record_url",
+      "result",
+      "adapter_error"
+    ],
+    "type": "object"
+  }
+]

removedOutput schema / properties

Removed value: -{
-  "contract_version": {
-    "const": "1.0",
-    "title": "Contract Version",
-    "type": "string"
-  },
-  "publication": {
-    "$ref": "#/$defs/PublicPublicationDetails"
-  },
-  "usage_boundary": {
-    "additionalProperties": true,
-    "title": "Usage Boundary",
-    "type": "object"
-  }
-}

removedOutput schema / required

Removed value: -[
-  "contract_version",
-  "publication",
-  "usage_boundary"
-]

removedOutput schema / title

Removed value: -"PublicationDetailsResponse"

Changed2 schema fields changedSep 2, 2026

addedOutput schema / $defs / PublicAbstractReuse

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "allowed": {
+      "default": false,
+      "title": "Allowed",
+      "type": "boolean"
+    },
+    "evidence_url": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "title": "Evidence Url"
+    },
+    "license": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "title": "License"
+    },
+    "source": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "title": "Source"
+    }
+  },
+  "title": "PublicAbstractReuse",
+  "type": "object"
+}

addedOutput schema / $defs / PublicPublicationDetails / properties / abstract_reuse
```
Added value: +{
+  "$ref": "#/$defs/PublicAbstractReuse"
+}
```

Changed1 schema field changedAug 25, 2026

addedInput schema / properties / pmid / description

Added value: +"One PubMed identifier to look up in Folklore's current corpus, as 1 to 12 digits without a PMID prefix."

AddedAug 13, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare read-only, idempotent, closed-world behavior, so safety is covered. The description adds that data comes from a specific derived corpus and that retraction status is surfaced, but says nothing about what happens when a PMID is absent from the corpus or how stale the data may be.

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?

A single front-loaded sentence with the action and scope stated first, followed by the field inventory. The field list is long but each item is informative rather than filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so the enumerated return fields are partly redundant. What is missing for a lookup tool is the not-found/miss behavior and any note on corpus coverage boundaries, which an agent would need to interpret an empty or error result.

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%, including the digit-only format and the 'no PMID prefix' constraint, so the schema does the heavy lifting. The description only restates 'one PMID' and adds no format or validation detail beyond it.

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?

States a specific verb and resource: 'Retrieve one PMID from the PubMed-derived genetics corpus', and enumerates the returned content. It is clear what the tool does, but it never differentiates itself from sibling search tools like search_literature_corpus or search_gene_literature.

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 by 'one PMID' — i.e. this is the fetch-by-identifier tool, used after a search returns a PMID. No explicit when-to-use, when-not-to-use, or named alternative is given.

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.