Skip to main content
Glama

Uniprot Get

uniprot_get
Read-onlyIdempotent

"Fetch protein [P12345]" / "UniProt entry for [accession]" / "FASTA sequence for [protein]", single UniProtKB entry by accession (e.g. P12345 or P38398 for BRCA1_HUMAN). Returns full protein record: sequence, function annotations, GO terms, cross-refs, post-translational modifications, variants. Pass format=fasta for sequence only.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

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

Input Schema

NameRequiredDescriptionDefault
formatNojson (default) | fasta | xml | txt | gff
accessionYese.g. "P12345" or "P38398" (BRCA1_HUMAN)

Output Schema

NameRequiredDescriptionDefault
featuresNoSequence features and annotations
sequenceNoAmino acid sequence
entryTypeNoEntry type (Swiss-Prot or TrEMBL)
uniProtkbIdNoUniProtKB identifier
primaryAccessionNoPrimary UniProt accession
proteinDescriptionNoProtein description and names

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds value by enumerating the record contents returned (sequence, function, GO terms, cross-refs, PTMs, variants) and the format override, though it says nothing about behavior on invalid accessions or response size.

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 core sentence is dense and front-loaded with the operation and expected inputs. The three quoted request phrasings overlap heavily in intent and are somewhat redundant keyword padding, but they aid matching against user wording and no sentence is wasted.

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?

With annotations covering safety and idempotency, a full output schema, and 100% schema coverage, the description supplies what remains: purpose, format behavior and record content. It is nearly complete for this simple two-parameter read tool; only error/invalid-accession behavior is absent.

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 baseline is 3, but the description adds real meaning beyond the schema: it explains what format=fasta yields (sequence only) where the schema merely lists allowed values. It also clarifies that accession can be a UniProt accession or a mnemonic-style identifier like BRCA1_HUMAN.

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 states a specific verb and resource: 'single UniProtKB entry by accession', and gives concrete accessions (P12345, P38398/BRCA1_HUMAN). An agent can tell it fetches one record rather than searching, distinguishing it in practice from uniprot_search, though the sibling is never named explicitly.

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?

Usage is implied through the quoted request phrasings ('Fetch protein [P12345]', 'FASTA sequence for [protein]') and the instruction to pass format=fasta for sequence-only needs, which gives clear context. No explicit when-not-to-use condition or named alternative (e.g. uniprot_search) is provided.

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.