Skip to main content
Glama

Get Diseases for Gene

get_diseases_for_gene
Read-onlyIdempotent

Return diseases associated with a gene (symbol or NCBI ID). Supports paging and verbosity levels.

Instructions

Return diseases associated with a gene (symbol or NCBI id). Signature: get_diseases_for_gene(gene, limit=, offset=, response_mode=).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
geneYesA gene symbol (e.g. 'PAX6') or NCBI gene CURIE (e.g. 'NCBIGene:5080'). Bare NCBI numeric ids (e.g. '5080') are also accepted.
limitNoMax diseases to return (default 25).
offsetNoRows to skip for forward paging (default 0).
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
totalNo
returnedNo
limitNo
offsetNo
next_offsetNo
truncatedNo
hpo_versionNo
recommended_citationNo
Behavior3/5

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

Annotations already cover readOnlyHint, destructiveHint, idempotentHint, openWorldHint. Description adds the function signature but lacks additional behavioral details like data source currency or error handling.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two efficient sentences: first states purpose, second shows signature. Front-loaded and no wasted words.

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?

Adequate for a straightforward query tool with output schema. Mentions response_mode but relies on schema for details. Could hint at common use cases or pagination behavior.

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 baseline is 3. Description does not add extra meaning beyond listing parameters in the signature; no elaboration on each parameter.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states 'Return diseases associated with a gene' with specific input types (symbol or NCBI id). Distinguishes from sibling tools like get_diseases_for_phenotype which use different input.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Description indicates core usage but does not explicitly exclude alternative tools or provide when-not guidance. Context from sibling names implies differentiation.

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/hpo-link'

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