Skip to main content
Glama

protein-mcp-server

protein-mcp-server: get annotations

protein_get_annotations
Read-only

Sequence and functional annotation for a protein: UniProt positional features (domains, binding and active sites, PTMs including cross-links and lipidation, topology, DNA binding, processing products such as chains and signal peptides, mutagenesis), natural variants, and InterPro domain/family memberships (Pfam, PROSITE, …) with GO terms. Provide a canonical UniProt accession directly, or a PDB ID — it is resolved to its UniProt accession via the structure's sequence cross-reference. A multi-chain PDB entry can map to several accessions; the default pick is deterministic (lowest author chain ID) and the alternatives are listed in "ambiguity" — pass "chain" to select a specific one. An accession UniProt merged into another entry answers for that successor with a notice; a demerged or deleted one fails with its replacement accessions. Use "include" to scope which annotation classes are fetched. Every response carries an "attribution" block with the upstream data licenses and citations.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "protein_get_annotations"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainNoAuthor chain ID (auth_asym_id, e.g. "A") that disambiguates a multi-chain PDB entry to a specific UniProt accession. Case-sensitive — must match the author chain ID exactly (large structures can carry distinct "A" and "a" chains). Only applies with pdb_id; ignored when uniprot is supplied directly. See polymerEntities[].authAsymIds in the pdb://{entry_id} resource for an entry's author chain IDs.
limitNoPer-class page size (1–200, default 50). Continue each class independently with features_offset, variants_offset, or domains_offset; the notice gives the next offset.
pdb_idNoPDB entry ID; resolved to a UniProt accession via cross-reference.
includeNoWhich annotation classes to fetch: features, domains (InterPro), variants, or all.all
uniprotNoCanonical UniProt accession (e.g. P69905). Isoform accessions (e.g. P04637-2) are rejected; UniProt annotates the canonical entry. Takes precedence over pdb_id.
domains_offsetNoZero-based offset into InterPro memberships; independent of features and variants.
features_offsetNoZero-based offset into functional features; independent of variants and domains.
variants_offsetNoZero-based offset into natural variants; independent of features and domains.

Output Schema

NameRequiredDescriptionDefault
errorNoPresent when the call failed. Absent on success.
noticeNoThe merge when UniProt merged the requested accession into another entry, first; then per class: the next offset, advice to lower an exhausted offset, an empty class, or an InterPro walk that stopped short of its count.
domainsNoInterPro domain/family memberships.
featuresNoPositional features other than natural variants, in UniProt order (grouped by type). Secondary structure, isoform sequences, and sequence-record notes are not included.
functionNoUniProt function summary.
organismNoSource organism scientific name.
variantsNoNatural sequence variants.
accessionNoUniProt accession the annotations describe — the successor when UniProt merged the requested accession, which the notice names.
ambiguityNoAlternative UniProt mappings when a PDB ID resolved ambiguously (no chain given).
geneNamesNoGene names.
truncatedNoTrue when at least one requested class has records past its returned page (the notice gives the next offset), or InterPro paging stopped before retrieving every membership.
attributionNoUpstream data-source licenses and citations for every source that contributed to this response. Always present — the attribution obligation travels with the data.
proteinNameNoRecommended protein name.
domainsTotalNoInterPro's membership count for the protein; present only when requested. When InterPro paging stopped short of it, the notice names how many memberships domains_offset can reach.
resolvedFromNoPDB ID the accession was resolved from, when applicable.
featuresTotalNoTotal positional features in the entry; present only when requested.
variantsTotalNoTotal natural variants in the entry; present only when requested.
sequenceLengthNoSequence length in residues.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Well beyond the readOnlyHint/openWorldHint annotations, the description discloses the deterministic default chain pick (lowest author chain ID), that alternatives appear in an "ambiguity" block, that merged accessions answer for the successor with a notice, that demerged/deleted accessions fail with replacements, and that every response carries an attribution block. Those are exactly the non-obvious behaviors an agent needs before calling.

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?

Front-loaded with the purpose, then input routing, then edge cases — a logical order with no wasted framing sentences. The feature enumeration in the first sentence is long (cross-links, lipidation, topology, signal peptides, mutagenesis), which is informative but the densest part of an otherwise tight definition.

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?

For an 8-parameter, open-world read tool with a full output schema, the description covers purpose, both input modes, chain disambiguation, accession lifecycle edge cases, class scoping, and the attribution block. Nothing an agent needs in order to call this correctly is missing, and return-format detail is correctly left to the output schema.

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 coverage is 100%, so the baseline is 3; the description still adds meaning the schema does not carry, notably why "chain" exists (multi-chain PDB entries mapping to several accessions) and the default resolution policy behind the ambiguity block. It does not add much on the offset/pagination parameters, which the schema already documents.

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?

States a specific verb and resource ("Sequence and functional annotation for a protein") and then enumerates the annotation classes returned: UniProt positional features, natural variants, InterPro memberships with GO terms. This is clearly distinguishable from the sibling structure-oriented tools (protein_get_structure, protein_compare_structures) without opening any schema.

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?

Gives concrete input-routing guidance: supply a canonical UniProt accession directly, or a PDB ID which is resolved via sequence cross-reference, and use "include" to scope the annotation classes. It also covers the edge cases (multi-chain PDB entries, merged/demerged/deleted accessions). It never names a sibling tool or states an explicit exclusion, so it stops short of a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.