Skip to main content
Glama

Orphan Disease Opportunity Atlas MCP

Get Myelofibrosis & Orphan Case Study

get_disease_case_study
Read-onlyIdempotent

Retrieve curated biology, NCT trials, GEO/PDB datasets, and failure modes (Flagships: 'jak2-myelofibrosis' and 'autoimmune-myelofibrosis').

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "disease_id": "autoimmune-myelofibrosis"
    },
    "name": "get_disease_case_study"
  }
}

Input Schema

NameRequiredDescriptionDefault
disease_idNojak2-myelofibrosis | autoimmune-myelofibrosis (+4 curated slugs).jak2-myelofibrosis

Output Schema

NameRequiredDescriptionDefault
case_studyYes
disease_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / disease_id / description
      Previous value: -"Flagship slug ('jak2-myelofibrosis' or 'autoimmune-myelofibrosis') or comparative cohort ('vexas-syndrome', 'castleman-disease', 'systemic-mastocytosis', 'telomere-biology-disorders')."New value: +"jak2-myelofibrosis | autoimmune-myelofibrosis (+4 curated slugs)."
    • addedOutput schema / required
      Added value: +[
      +  "disease_id",
      +  "case_study"
      +]
  2. Changed2 schema fields changed
    • changedInput schema / properties / disease_id / description
      Previous value: -"Indication slug: 'jak2-myelofibrosis' or 'autoimmune-myelofibrosis'."New value: +"Flagship slug ('jak2-myelofibrosis' or 'autoimmune-myelofibrosis') or comparative cohort ('vexas-syndrome', 'castleman-disease', 'systemic-mastocytosis', 'telomere-biology-disorders')."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "case_study": {
      +      "type": "object"
      +    },
      +    "disease_id": {
      +      "type": "string"
      +    }
      +  },
      +  "type": "object"
      +}
  3. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "disease_id": "autoimmune-myelofibrosis"
      +  }
      +]
    • changedInput schema / properties / disease_id / description
      Previous value: -"Disease identifier: 'jak2-myelofibrosis' (clonal JAK2 V617F+ PMF) or 'autoimmune-myelofibrosis' (AIMF / SLE-associated reversible marrow fibrosis + iron overload)."New value: +"Indication slug: 'jak2-myelofibrosis' or 'autoimmune-myelofibrosis'."
  4. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so the safety profile needs no restating. The description earns credit for disclosing the content categories and the two flagship slugs, but says nothing about what happens with an unknown slug, whether the data is cached/static, or response size — relevant given a curation-backed 'case study' payload.

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?

One sentence with the verb and payload front-loaded; every clause carries content. The trailing parenthetical of flagship slugs is slightly awkward but informative rather than filler.

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 needn't explain return values, and the single parameter is fully documented in schema. The remaining gap is discoverability — the schema mentions '+4 curated slugs' without saying how to enumerate them or find them via a search sibling.

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% and the single parameter already carries a default and a pipe-delimited list of valid values, so the schema does the heavy lifting. The description adds only the flagship slug names, which the schema itself already lists, so a baseline 3 is appropriate.

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 pairs a specific verb ('Retrieve') with a concrete resource and enumerates the payload categories (biology, NCT trials, GEO/PDB datasets, failure modes), so an agent knows exactly what comes back. It does not explicitly contrast itself with siblings like search_any_orphan_indication, which keeps it just 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 Guidelines2/5

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

There is no statement of when to use this tool versus alternatives, nor any precondition such as 'call only when you already have a curated disease slug.' The only hint is the parenthetical naming of two flagship slugs, which implies a known-slug lookup but never says so.

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.