Skip to main content
Glama
orphan-disease-opportunity-mcp

orphan-disease-opportunity-mcp

get_disease_case_study

Retrieve biological tractability, standard-of-care failure modes, FDA Orphan Drug Act unit economics, and open structural or transcriptomic datasets for an orphan disease indication.

Instructions

Retrieve biological tractability, standard-of-care failure modes (e.g. Type I JH1 JAK inhibitor cytopenias vs JH2 V617F mutant selectivity), FDA Orphan Drug Act unit economics, and open structural/transcriptomic datasets for an orphan indication.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault
disease_idNoDisease identifier (default Flagship #1: 'jak2-myelofibrosis').jak2-myelofibrosis

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. 'Retrieve' implies a read-only lookup and the content enumeration usefully discloses what categories come back, but nothing is said about permissions, whether the identifier must exist, error/fallback behavior, or cost of the deep research payload.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single front-loaded sentence, but that sentence is a heavy noun-phrase list packed with unexplained jargon; the parenthetical 'Type I JH1 JAK inhibitor cytopenias vs JH2 V617F mutant selectivity' consumes substantial space without helping tool selection.

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?

For a one-parameter tool with no annotations and no output schema, the enumeration of returned content categories substitutes reasonably well for a return-value description. The main omissions are the default indication and behavior for an unrecognized disease_id.

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 coverage is 100% and the single disease_id parameter is already documented with its default. The description adds only the implicit framing that the lookup is scoped to one 'orphan indication' per call; it never mentions the identifier, its default, or accepted formats.

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 verb 'Retrieve' plus 'case study ... for an orphan indication' identifies the resource, and the enumerated contents (tractability, SoC failure modes, orphan-drug economics, datasets) make the payload concrete. It is clearly distinct from the sibling tools (validation communities, grants, founder matching, feedback), though the dense scientific parenthetical blurs the headline purpose somewhat.

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 explicit when-to-use or when-not-to-use guidance, and no alternative tool is named. The only implied context is 'looking up an orphan indication', which the agent has to infer from the parameter and the content list.

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