Skip to main content
Glama

Orphan Disease Opportunity Atlas MCP

Get 90-Day Diligence Roadmap

get_90_day_validation_plan
Read-onlyIdempotent

Retrieve a structured 30/60/90-day diligence roadmap contrasting Clonal JAK2+ vs Autoimmune Myelofibrosis (plus 4 adjacent cohorts).

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": "jak2-myelofibrosis"
    },
    "name": "get_90_day_validation_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
backgroundNocomputational-ai-bio | public-health | venture-novel-financing | allcomputational-ai-bio
disease_idNojak2-myelofibrosis | autoimmune-myelofibrosis (+4 cohorts)jak2-myelofibrosis
capital_tierNobootstrapped-grant | seed | series-a-platform | allbootstrapped-grant
wet_lab_requiredNoFalse=zero-wet-lab; true=wet-lab.

Output Schema

NameRequiredDescriptionDefault
disease_idYes
roadmap_30_60_90Yes
recommended_grantsNo
matched_blueprint_milestonesNo
flagship_myelofibrosis_contrastYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/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, non-destructive behavior, so the safety profile is fully covered. The description adds that the output is structured as a 30/60/90-day plan and is comparative across cohorts, which is modest but real context beyond the annotations. It says nothing about depth, cohort coverage mechanics, or scoring methodology.

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 front-loaded sentence with no filler. The trailing parenthetical '(plus 4 adjacent cohorts)' is slightly vague since it neither names them nor says how they are selected, but it is compact enough not to be wasteful.

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?

With a rich output schema and complete annotation coverage, the description only needs to convey purpose and selection guidance. It conveys purpose but omits when-to-use versus siblings and how the roadmap changes with capital_tier or wet_lab_required, leaving a real gap for a planning-oriented tool with four optional parameters.

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 disease_id, background, capital_tier, and wet_lab_required are already fully documented with allowed values. The description mentions cohort comparison, which loosely maps to disease_id, but adds no new meaning about what capital_tier or wet_lab_required do to the returned roadmap. Baseline 3 applies.

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 ('Retrieve') and a specific resource ('structured 30/60/90-day diligence roadmap') and names the compared cohorts (Clonal JAK2+ vs Autoimmune Myelofibrosis plus 4 adjacent cohorts). This is more specific than the title alone, but it never distinguishes itself from siblings like get_disease_case_study or get_validation_communities, which could plausibly also return disease-level diligence content.

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 guidance on when to use this roadmap rather than get_disease_case_study or get_validation_communities, and no stated prerequisites or exclusions. The agent must infer the choice from names alone.

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.