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

orphan-disease-opportunity-mcp

get_validation_communities

Retrieve established rare-disease patient and hematology clinical networks with non-extractive ethical guidelines to validate founder problem discovery.

Instructions

Return established rare-disease patient & hematology clinical networks plus strict non-extractive ethical guidelines for founder problem discovery.

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

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states what is returned but does not clarify that this is a read-only lookup, whether the disease ID affects network selection, what the ethical guidelines consist of, or any operational constraints like rate limits or authentication.

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 definition is a single front-loaded sentence with no wasted framing. It is efficient, though the trailing phrase 'for founder problem discovery' is slightly jargon-heavy and could be clearer without losing value.

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?

For a low-complexity read tool with one optional parameter and no output schema, the description gives a reasonable summary of the return contents. However, with no annotations and no output schema, it should do more to explain what the agent receives and how disease_id shapes the result.

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 disease_id parameter is fully documented with a default. The description adds no further meaning about how the identifier influences the returned networks or guidelines, so the baseline of 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 uses a specific verb ('Return') and names the resource ('established rare-disease patient & hematology clinical networks plus strict non-extractive ethical guidelines'). It distinguishes the tool from siblings like get_disease_case_study and find_non_dilutive_grants, though the phrase 'founder problem discovery' is somewhat abstract and does not fully sharpen the scope.

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 implies a use case ('founder problem discovery') but provides no explicit guidance on when to choose this tool over alternatives such as match_founder_opportunities or get_disease_case_study. It also lacks any when-not-to-use or prerequisite information.

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