Skip to main content
Glama

Folklore Clinical Variant Interpretation MCP

Find genes associated with a disease

search_disease_genes
Read-onlyIdempotent

Find genes associated with an exact MONDO identifier or disease-name search. Returns ClinGen validity assertions with inheritance, source reports and snapshot provenance. Name searches can return multiple disease identities.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "disease": "<disease>"
    },
    "name": "search_disease_genes"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of source assertions per page, from 1 to 50.
offsetNoZero-based assertion offset; use the returned nextOffset when present.
diseaseYesOne public disease name or exact MONDO identifier (MONDO: followed by seven digits). A name search may match multiple distinct diseases.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • changedInput schema / properties / disease / description
      Previous value: -"One public disease name or exact MONDO identifier (MONDO: followed by seven digits). A name search may match multiple distinct diseases. No symptoms or patient narrative."New value: +"One public disease name or exact MONDO identifier (MONDO: followed by seven digits). A name search may match multiple distinct diseases."
    • removedOutput schema / $defs / UsageBoundary
      Removed value: -{
      -  "additionalProperties": false,
      -  "properties": {
      -    "intended_use": {
      -      "const": "professional_gene_disease_review",
      -      "title": "Intended Use",
      -      "type": "string"
      -    },
      -    "not_for": {
      -      "items": {
      -        "enum": [
      -          "patient_diagnosis",
      -          "treatment_decision",
      -          "variant_pathogenicity_classification"
      -        ],
      -        "type": "string"
      -      },
      -      "title": "Not For",
      -      "type": "array"
      -    },
      -    "patient_context_evaluated": {
      -      "const": false,
      -      "title": "Patient Context Evaluated",
      -      "type": "boolean"
      -    },
      -    "review_required": {
      -      "const": true,
      -      "title": "Review Required",
      -      "type": "boolean"
      -    }
      -  },
      -  "required": [
      -    "intended_use",
      -    "patient_context_evaluated",
      -    "review_required",
      -    "not_for"
      -  ],
      -  "title": "UsageBoundary",
      -  "type": "object"
      -}
    • removedOutput schema / additionalProperties
      Removed value: -false
    • addedOutput schema / anyOf
      Added value: +[
      +  {
      +    "additionalProperties": false,
      +    "properties": {
      +      "associations": {
      +        "items": {
      +          "$ref": "#/$defs/Association"
      +        },
      +        "maxItems": 50,
      +        "title": "Associations",
      +        "type": "array"
      +      },
      +      "contractVersion": {
      +        "const": "2",
      +        "title": "Contractversion",
      +        "type": "string"
      +      },
      +      "pagination": {
      +        "$ref": "#/$defs/Pagination"
      +      },
      +      "query": {
      +        "$ref": "#/$defs/Query"
      +      },
      +      "source": {
      +        "$ref": "#/$defs/Source"
      +      },
      +      "status": {
      +        "enum": [
      +          "ok",
      +          "not_found"
      +        ],
      +        "title": "Status",
      +        "type": "string"
      +      },
      +      "warnings": {
      +        "items": {
      +          "type": "string"
      +        },
      +        "title": "Warnings",
      +        "type": "array"
      +      }
      +    },
      +    "required": [
      +      "contractVersion",
      +      "status",
      +      "query",
      +      "associations",
      +      "pagination",
      +      "source",
      +      "warnings"
      +    ],
      +    "title": "GeneDiseaseResponse",
      +    "type": "object"
      +  },
      +  {
      +    "additionalProperties": false,
      +    "properties": {
      +      "adapter_error": {
      +        "additionalProperties": false,
      +        "properties": {
      +          "code": {
      +            "type": "string"
      +          },
      +          "message": {
      +            "type": "string"
      +          },
      +          "retryable": {
      +            "type": "boolean"
      +          }
      +        },
      +        "required": [
      +          "code",
      +          "message",
      +          "retryable"
      +        ],
      +        "type": "object"
      +      },
      +      "contractVersion": {
      +        "const": "2"
      +      }
      +    },
      +    "required": [
      +      "contractVersion",
      +      "adapter_error"
      +    ],
      +    "type": "object"
      +  }
      +]
    • removedOutput schema / properties
      Removed value: -{
      -  "associations": {
      -    "items": {
      -      "$ref": "#/$defs/Association"
      -    },
      -    "maxItems": 50,
      -    "title": "Associations",
      -    "type": "array"
      -  },
      -  "contractVersion": {
      -    "const": "1.0",
      -    "title": "Contractversion",
      -    "type": "string"
      -  },
      -  "pagination": {
      -    "$ref": "#/$defs/Pagination"
      -  },
      -  "query": {
      -    "$ref": "#/$defs/Query"
      -  },
      -  "source": {
      -    "$ref": "#/$defs/Source"
      -  },
      -  "status": {
      -    "enum": [
      -      "ok",
      -      "not_found"
      -    ],
      -    "title": "Status",
      -    "type": "string"
      -  },
      -  "usage_boundary": {
      -    "$ref": "#/$defs/UsageBoundary"
      -  },
      -  "warnings": {
      -    "items": {
      -      "type": "string"
      -    },
      -    "title": "Warnings",
      -    "type": "array"
      -  }
      -}
    • removedOutput schema / required
      Removed value: -[
      -  "contractVersion",
      -  "status",
      -  "query",
      -  "associations",
      -  "pagination",
      -  "source",
      -  "warnings",
      -  "usage_boundary"
      -]
    • removedOutput schema / title
      Removed value: -"GeneDiseaseResponse"
  2. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds genuine behavioral context beyond that: it reveals the payload is ClinGen validity assertions with inheritance and source reports, includes snapshot provenance, and that name searches may resolve to multiple disease identities — all things an agent could not infer from annotations.

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 short sentences, front-loaded with the core action and return content, then the name-search caveat. No filler; each sentence carries information, though the caveat partially duplicates the schema.

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?

An output schema exists, so return-value detail isn't required, and the description still characterizes the result payload. Combined with full schema coverage and safety annotations, an agent has enough to call this correctly; only the missing sibling comparison keeps it from 5.

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 three parameters are documented in the schema, establishing the baseline of 3. The description adds only the pairing of 'disease' with exact MONDO identifiers or names and the multi-match caveat, both of which are essentially restated in the schema's parameter descriptions.

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 gives a specific verb+resource ('Find genes associated with a disease') and states what is returned (ClinGen validity assertions with inheritance, source reports, snapshot provenance). It does not explicitly differentiate itself from the sibling get_gene_disease_associations, which is the closest alternative, so it falls short of a 5.

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?

The description implies lookup mode ('exact MONDO identifier or disease-name search') and warns that name searches can return multiple disease identities, which is a useful usage cue. However, it never says when to prefer this over get_gene_disease_associations or resolve_gene, and no exclusion conditions are stated.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.