Skip to main content
Glama

Orphan Disease Opportunity Atlas MCP

Get Validation Registries & Guardrails

get_validation_communities
Read-onlyIdempotent

Retrieve registries, biobanks, patient foundations, and non-extractive research guardrails for Myelofibrosis and rare diseases.

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_validation_communities"
  }
}

Input Schema

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

Output Schema

NameRequiredDescriptionDefault
disease_idYes
ethical_discovery_guidelinesNo
institutional_and_patient_communitiesNo

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 slug."New value: +"jak2-myelofibrosis | autoimmune-myelofibrosis (+4 cohorts)."
    • addedOutput schema / required
      Added value: +[
      +  "disease_id"
      +]
  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 slug."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "disease_id": {
      +      "type": "string"
      +    },
      +    "ethical_discovery_guidelines": {
      +      "type": "array"
      +    },
      +    "institutional_and_patient_communities": {
      +      "type": "array"
      +    }
      +  },
      +  "type": "object"
      +}
  3. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "disease_id": "jak2-myelofibrosis"
      +  }
      +]
    • changedInput schema / properties / disease_id / description
      Previous value: -"Disease identifier ('jak2-myelofibrosis' or 'autoimmune-myelofibrosis')."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=true, openWorldHint=false, idempotentHint=true, and destructiveHint=false, so the safety and idempotency profile is covered. The description adds useful content about what is retrieved (registries, biobanks, foundations, guardrails), but does not disclose anything further about behavior beyond that, such as result scope or limitations. A 3 is appropriate given the annotation coverage.

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?

The description is a single front-loaded sentence with no filler. It is efficient and easy to parse, though the phrase "non-extractive research guardrails" is somewhat specialized jargon that could slow interpretation.

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?

This is a read-only retrieval tool with annotations covering safety and idempotency, a fully described single parameter in the schema, and an output schema. The description adequately explains what is returned at a high level without needing to enumerate return values. It is complete enough for an agent to call correctly.

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 there is only one optional disease_id parameter with a default and examples, so the schema carries the parameter documentation burden. The description implies disease scoping but adds no syntax or format details beyond what the schema already provides. Baseline 3 is correct here.

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 names a specific verb ("Retrieve") and concrete resource types ("registries, biobanks, patient foundations, and non-extractive research guardrails") scoped to Myelofibrosis and rare diseases. This is clearly more than a restatement of the tool name, though it does not explicitly distinguish itself from siblings such as get_90_day_validation_plan.

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?

The description provides disease context ("for Myelofibrosis and rare diseases") but gives no explicit when-to-use guidance, no exclusions, and no alternatives. An agent must infer when to choose this over related validation-plan or case-study tools.

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.