Skip to main content
Glama
berntpopp
by berntpopp

Get Disease Genes

get_disease_genes
Read-onlyIdempotent

Retrieve gene-disease associations for a rare disease from Orphanet, including gene symbol, HGNC ID, association type, and cross-references to OMIM and Ensembl.

Instructions

Return gene-disease associations for an Orphanet disorder: gene symbol, HGNC id, association type, and cross-references (OMIM, Ensembl, etc.). Signature: get_disease_genes(term, response_mode=).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
termYesAn ORPHAcode (ORPHA:166024 or 166024), a disease label/synonym, or an external xref CURIE that resolves to a single Orphanet term.
response_modeNoVerbosity: minimal|compact|standard|full (default compact).compact

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
successNo
_metaNo
error_codeNo
messageNo
retryableNo
recovery_actionNo
fieldNo
allowed_valuesNo
hintNo
candidatesNo
orpha_codeNo
nameNo
countNo
genesNo
Behavior3/5

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

Annotations already provide safety and idempotency hints. The description adds context about return fields but doesn't disclose behavioral traits like response size limits, pagination, or performance considerations. It does not contradict annotations.

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 very concise with two sentences and a signature. It front-loads the main purpose. Minor redundancy with the 'Signature:' line, but overall efficient.

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?

Given the rich output schema and many sibling tools, the description adequately explains the primary function but lacks differentiation from similar tools. It provides enough for a basic understanding but could be more complete with usage context.

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%, so parameters are fully documented in the schema. The description adds no additional semantic detail beyond the signature and implicit return field names. Baseline 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 clearly states it returns gene-disease associations for a specific Orphanet disorder, listing fields like gene symbol and cross-references. It distinguishes from siblings by specifying the direction (genes for a disease) and the specific data fields.

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?

The description implies usage for retrieving gene associations of a disease, with examples for the 'term' parameter showing valid inputs. However, it does not explicitly state when to use this tool versus alternatives like find_diseases_by_gene or get_disease, missing guidance on selection criteria.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/berntpopp/orphanet-link'

If you have feedback or need assistance with the MCP directory API, please join our Discord server