Skip to main content
Glama

Uniprot Search

uniprot_search
Read-onlyIdempotent

"Find protein [name]" / "look up [gene] in UniProt" / "BRCA1 / TP53 / insulin protein info" / "all proteins for [organism]", UniProtKB search via Lucene-style queries (e.g. gene:BRCA1 AND organism_id:9606 for human BRCA1). UniProt is the authoritative protein-sequence-and-function database, use for protein characterization, function annotation, sequence retrieval, and cross-references to PDB/GO/PubMed.

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": {
      "query": "gene:BRCA1 AND organism_id:9606"
    },
    "name": "uniprot_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
sizeNo1-500 (default 25)
queryYesLucene-style expression, passed bare, do NOT wrap the whole thing in quotes. Fielded terms combine with AND, e.g. gene:BRCA1 AND organism_id:9606. Quotes are only for a multi-word value, e.g. organism_name:"Homo sapiens". Plain-English questions match poorly because every token must appear; prefer keywords.
fieldsNoComma-sep returned fields (json/tsv only).
formatNojson (default) | tsv | fasta | xml

Output Schema

NameRequiredDescriptionDefault
facetsNoSearch facets for filtering
resultsNoArray of search result entries

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / query / description
      Previous value: -"Lucene-style expression, passed bare — do NOT wrap the whole thing in quotes. Fielded terms combine with AND, e.g. gene:BRCA1 AND organism_id:9606. Quotes are only for a multi-word value, e.g. organism_name:\"Homo sapiens\". Plain-English questions match poorly because every token must appear; prefer keywords."New value: +"Lucene-style expression, passed bare, do NOT wrap the whole thing in quotes. Fielded terms combine with AND, e.g. gene:BRCA1 AND organism_id:9606. Quotes are only for a multi-word value, e.g. organism_name:\"Homo sapiens\". Plain-English questions match poorly because every token must appear; prefer keywords."
  2. Added

TDQS

A3.6/5.0
Behavior3/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 that queries are Lucene-style and that plain-English questions match poorly because every token must appear, which is genuine behavioral guidance. It says nothing about rate limits, pagination behavior beyond what the schema states, or result ordering.

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-loads recognizable user phrasings, then the technical mechanism and domain rationale, all in one compact block with no filler paragraphs. There is mild redundancy where the Lucene example and the plain-English caveat duplicate the query parameter description.

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 100% schema coverage and an output schema, the description need not explain return values, and it correctly focuses on when to reach for UniProt and how to phrase queries. The only minor gap is that the distinction between search and single-entry retrieval is left implicit.

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% and each of the four parameters (query, size, fields, format) is documented in-schema with examples. The description repeats the same gene:BRCA1 / organism_id:9606 example and the fielded-term syntax already present in the query parameter description, so it adds little beyond the schema. Baseline 3 is appropriate.

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?

States a specific verb and resource ('UniProtKB search via Lucene-style queries') and frames the domain ('authoritative protein-sequence-and-function database'), plus enumerates the tasks it serves (characterization, function annotation, sequence retrieval, cross-references). It does not explicitly differentiate itself from a lookup-by-accession sibling such as uniprot_get, so it stops short of a 5.

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 clear user-intent triggers ('Find protein [name]', 'look up [gene] in UniProt', 'all proteins for [organism]') that map situations to this tool, which is stronger than implied usage. It offers no when-not conditions or named alternative for retrieving a single known entry, so it is clear context without exclusions.

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.