Skip to main content
Glama

Orphan Disease Opportunity Atlas MCP

Search Any of 7,000+ Orphan Diseases (Live)

search_any_orphan_indication
Read-onlyIdempotent

Search live OpenTargets, ClinicalTrials.gov v2, and PubMed evidence for any rare disease, benchmarked against JAK2+ & 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_query": "JAK2 V617F myelofibrosis"
    },
    "name": "search_any_orphan_indication"
  }
}

Input Schema

NameRequiredDescriptionDefault
disease_queryYesRare disease (e.g., 'JAK2 V617F myelofibrosis', 'autoimmune myelofibrosis').
founder_backgroundNocomputational-ai-bio | public-health | venture-novel-financing | all.all

Output Schema

NameRequiredDescriptionDefault
queryYes
live_diligenceYes
matched_grantsNo
curated_atlas_matchNo
fda_orphan_unit_economicsYes
flagship_myelofibrosis_benchmarkNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly, openWorld, idempotent and non-destructive, so the safety profile is covered. The description adds real value by naming the three live external data sources, which tells the agent results come from third-party services. It stops short of disclosing latency, rate limits, behavior on no-hit queries, or what the 'benchmark' actually does.

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 sentence that front-loads the verb, the data sources and the disease scope, with no filler. The closing benchmark clause is the one piece that does not clearly earn its place, as it reads as unexplained jargon.

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 return values need not be explained in prose. However, for a tool that fans out to three live external APIs, the definition says nothing about expected latency, partial-source failures, or empty results, and the unexplained benchmarking claim leaves a gap an agent could misread.

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% with only two parameters, so the schema already carries the semantics and the baseline of 3 applies. The description adds nothing about query formatting for disease_query, and notably never mentions founder_background despite it being a non-obvious second parameter.

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?

Names a specific verb (Search) and resource (live OpenTargets, ClinicalTrials.gov v2, and PubMed evidence) scoped to rare/orphan diseases, which is enough to distinguish it from case-study and opportunity-listing siblings. The trailing 'benchmarked against JAK2+ & Autoimmune Myelofibrosis' clause muddies rather than sharpens the purpose, since it is unclear whether that is a fixed comparison or just an example.

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: the agent can infer this is the tool for pulling external evidence on a named rare disease. There is no explicit when-to-use framing, no statement of when another sibling (e.g., get_disease_case_study or get_90_day_validation_plan) is the better choice, and no prerequisites or exclusions.

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.