Skip to main content
Glama
berntpopp
by berntpopp

Get Protein Diseases

get_protein_diseases
Read-onlyIdempotent

Retrieve disease annotations for a given UniProt protein accession: disease name, ID, MIM number, definition, and involvement in the entry.

Instructions

Return disease annotations associated with an entry: disease name, UniProt disease id, mnemonic, MIM id, the clinical definition (the disease vocabulary's own description), and involvement (the entry-specific note). Pairs with get_protein_variants for variant-level disease evidence. Signature: get_protein_diseases(accession).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
accessionYesUniProtKB accession, e.g. P05067 (isoforms like P05067-2 accepted).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
successNo
_metaNo
error_codeNo
messageNo
retryableNo
recovery_actionNo
fieldNo
allowed_valuesNo
hintNo
accessionNo
countNo
diseasesNo
Behavior4/5

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

Annotations already indicate read-only, non-destructive, idempotent behavior; description adds value by detailing output fields and pairing suggestion, without contradiction.

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 sentences, front-loaded with purpose, efficient and no wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With output schema present, description explains return fields adequately; single parameter and clear purpose make it complete.

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% with parameter description already including example; description does not add new semantics beyond the schema.

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 the tool returns disease annotations with specific fields listed (name, UniProt id, etc.) and distinguishes from sibling tool get_protein_variants.

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?

Explicitly pairs with get_protein_variants for variant-level evidence, providing clear context, though no explicit when-not-to-use is stated.

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

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