Skip to main content
Glama

get_annotations

Fetch UniProt protein annotations by accession and annotation type, providing detailed residue and region information for analysis.

Instructions

This tool retrieves all annotations for a specified UniProt residue range. It allows querying by the UniProt accession and the annotation type (e.g., MUTAGEN for AlphaMissense).

Arguments

  • qualifier (str): UniProt accession (e.g., 'Q5VSL9').

  • annotation_type (str): Type of annotation (e.g., 'MUTAGEN' for AlphaMissense).

Example Input:

  • qualifier: Q5VSL9

  • annotation_type: MUTAGEN

Response Structure

The response includes detailed information about the UniProt entry and its associated annotations.

Example Output:

{
  "accession": "Q5VSL9",
  "id": "STRP1_HUMAN",
  "sequence": "MEPAVGGPGPLIVNNKQPQPPPPPPPAAAQPPPGAPRAAAGLLPGGKAREFNRNQRKDSEGYSESPDLEFEYADTDKWAAELSELYSYTEGPEFLMNRKCFEEDFRIHVTDKKWTELDTNQHRTHAMRLLDGLEVTAREKRLKVARAILYVAQGTFGECSSEAEVQSWMRYNIFLLLEVGTFNALVELLNMEIDNSAACSSAVRKPAISLADSTDLRVLLNIMYLIVETVHQECEGDKAEWRTMRQTFRAELGSPLYNNEPFAIMLFGMVTKFCSGHAPHFPMKKVLLLLWKTVLCTLGGFEELQSMKAEKRSILGLPPLPEDSIKVIRNMRAASPPASASDLIEQQQKRGRREHKALIKQDNLDAFNERDPYKADDSREEEEENDDDNSLEGETFPLERDEVMPPPLQHPQTDRLTCPKGLPWAPKVREKDIEMFLESSRSKFIGYTLGSDTNTVVGLPRPIHESIKTLKQHKYTSIAEVQAQMEEEYLRSPLSGGEEEVEQVPAETLYQGLLPSLPQYMIALLKILLAAAPTSKAKTDSINILADVLPEEMPTTVLQSMKLGVDVNRHKEVIVKAISAVLLLLLKHFKLNHVYQFEYMAQHLVFANCIPLILKFFNQNIMSYITAKNSISVLDYPHCVVHELPELTAESLEAGDSNQFCWRNLFSCINLLRILNKLTKWKHSRTMMLVVFKSAPILKRALKVKQAMMQLYVLKLLKVQTKYLGRQWRKSNMKTMSAIYQKVRHRLNDDWAYGNDLDARPWDFQAEECALRANIERFNARRYDRAHSNPDFLPVDNCLQSVLGQRVDLPEDFQMNYDLWLEREVFSKPISWEELLQ",
  "annotation": [
    {
      "type": "MUTAGEN",
      "description": "AM score",
      "source_name": "AFDB",
      "source_url": "https://alphafold.ebi.ac.uk/files/AF-Q5VSL9-F1-aa-substitutions.csv",
      "evidence": "COMPUTATIONAL/PREDICTED",
      "residues": [1, 2, 3, ...],
      "regions": [
        {
          "start": 1,
          "end": 837,
          "annotation_value": [0.3234, 0.3281, ...],
          "unit": null
        }
      ]
    }
  ]
}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qualifierYes
output_jsonNo
annotation_typeNoMUTAGEN
Behavior3/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. It discloses the response structure with a detailed example, but it doesn't mention potential limitations, safety, or side effects. The 'residue range' vs 'accession' ambiguity also detracts from transparency.

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 well-structured with sections for arguments, example input, and response structure. The example output is quite extensive (including the full sequence), which is somewhat verbose but serves to clarify the return format.

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?

The description is fairly complete for a retrieval tool: it provides parameter meanings and an example output that compensates for the lack of an output schema. It falls short by not covering output_json and providing no usage guidance relative to sibling tools.

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

Parameters4/5

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

Schema description coverage is 0%, so the description compensates by explaining qualifier and annotation_type with examples. However, it completely omits the output_json parameter, which is part of the schema.

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 the tool retrieves annotations for a UniProt entry and explains the query parameters (accession and annotation type). However, the phrase 'residue range' is misleading since the qualifier is an accession, and it doesn't explicitly differentiate from siblings.

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 explains how to use the tool with arguments and an example, but it never states when to choose this tool over the sibling tools (get_alphafold_prediction, get_uniprot_summary) or provides any exclusion 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/zeinab-sheikhi/mcp-alphafold'

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