Skip to main content
Glama
pansapiens

uniprot-unipressed-mcp

by pansapiens

uniprot_fetch

Fetch specific protein entries by providing UniProt accession IDs. Supports multiple databases, custom fields, and JSON or TOON output.

Instructions

Fetch specific protein entries by their UniProt accession IDs.

Args: ids: List of UniProt accession IDs to fetch. Examples: - ["P62988"] - Single protein - ["A0A0C5B5G6", "A0A1B0GTW7"] - Multiple proteins

database: UniProt database to fetch from. One of: uniprotkb (default), uniparc, uniref

fields: Optional list of return fields to include. If not specified, all fields
    are returned. Available return fields (see https://www.uniprot.org/help/return_fields):
    
    Names & Taxonomy:
    - accession, id, gene_names, gene_primary, gene_synonym, gene_oln, gene_orf
    - organism_name, organism_id, protein_name, xref_proteomes
    - lineage, lineage_ids, virus_hosts
    
    Sequences:
    - cc_alternative_products, ft_var_seq, cc_sc_epred, fragment, encoded_in
    - length, mass, cc_mass_spectrometry, ft_variant, ft_non_cons, ft_non_std
    - ft_non_ter, cc_polymorphism, cc_rna_editing, sequence, cc_sequence_caution
    - ft_conflict, ft_unsure, sequence_version
    
    Function:
    - absorption, ft_act_site, cc_activity_regulation, ft_binding, cc_catalytic_activity
    - cc_cofactor, ft_dna_bind, ec, cc_function, kinetics, cc_pathway
    - ph_dependence, redox_potential, rhea, ft_site, temp_dependence
    
    Miscellaneous:
    - annotation_score, cc_caution, comment_count, feature_count, keywordid, keyword
    - cc_miscellaneous, protein_existence, reviewed, tools, uniparc_id
    
    Interaction:
    - cc_interaction, cc_subunit
    
    Expression:
    - cc_developmental_stage, cc_induction, cc_tissue_specificity
    
    Gene Ontology (GO):
    - go_p, go_c, go, go_f, go_id
    
    Pathology & Biotech:
    - cc_allergen, cc_biotechnology, cc_disruption_phenotype, cc_disease
    - ft_mutagen, cc_pharmaceutical, cc_toxic_dose
    
    Subcellular location:
    - ft_intramem, cc_subcellular_location, ft_topo_dom, ft_transmem
    
    PTM / Processing:
    - ft_chain, ft_crosslnk, ft_disulfid, ft_carbohyd, ft_init_met, ft_lipid
    - ft_mod_res, ft_peptide, cc_ptm, ft_propep, ft_signal, ft_transit
    
    Structure:
    - structure_3d, ft_strand, ft_helix, ft_turn
    
    Publications:
    - lit_pubmed_id
    
    Date:
    - date_created, date_modified, date_sequence_modified, version
    
    Family & Domains:
    - ft_coiled, ft_compbias, cc_domain, ft_domain, ft_motif, protein_families
    - ft_region, ft_repeat, ft_zn_fing
    
    Cross-references:
    - See https://www.uniprot.org/help/return_fields for cross-reference fields

response_format: Response format. One of: 'json' (default) or 'toon'.
    - 'json': Returns response in JSON format
    - 'toon': Returns response in TOON format

Returns: When response_format='json': JSON object with: - results: Array of fetched protein entries - found: Number of entries successfully retrieved - requested: Number of IDs that were requested

When response_format='toon': TOON-formatted string with:
- results: Array of fetched protein entries
- found: Number of entries successfully retrieved
- requested: Number of IDs that were requested

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idsYes
databaseNouniprotkb
fieldsNo
response_formatNojson

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

No annotations are provided, and the description lacks disclosure of behavioral traits such as rate limits, authentication requirements, or error handling for missing IDs. It only describes the return format but not edge cases or limitations.

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

Conciseness3/5

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

The description is well-structured with clear sections (Args, Returns), but it is overly verbose due to the exhaustive list of fields. This could be shortened or referenced externally for better conciseness.

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 absence of annotations and an output schema, the description provides adequate information about parameters and return format. However, it lacks details on error handling, performance considerations, or rate limits, leaving some gaps for a complete understanding.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description fully compensates by providing detailed parameter explanations, including examples, defaults, allowed values (enum for database and response_format), and an extensive list of available fields with categories.

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?

The description states 'Fetch specific protein entries by their UniProt accession IDs,' which is a specific verb+resource combination. It clearly differentiates from the sibling tool 'uniprot_search' by focusing on fetching by ID rather than searching.

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 does not explicitly specify when to use this tool versus alternatives. While the sibling name implies search vs. fetch, there is no guidance on when to choose one over the other or any conditions or prerequisites.

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/pansapiens/uniprot-unipressed-mcp'

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