Skip to main content
Glama
berntpopp
by berntpopp

Find Proteins

find_proteins
Read-onlyIdempotent

Search UniProtKB by gene, organism, keyword, EC number, or name to find matching protein entries with accession, mnemonic, and review status.

Instructions

Search UniProtKB by structured filters and return matching entries (accession, mnemonic, recommended name, reviewed flag, organism). Requires at least one anchor: gene symbol, mnemonic, EC number, keyword (KW-id or label), OR organism_taxon together with name_contains (matched per word, in any order, case-insensitive). Reviewed (Swiss-Prot) hits are ranked first. UniProt SPARQL has no general full-text index, so for broad text use search_example_queries or run_sparql_query. Pair with get_protein for full detail. Results are ordered reviewed-first, then by mnemonic, then accession (stable across pages). Cold search can take several seconds; an identical repeat is cached (~0 ms). If you already know the accession, call get_protein directly -- it is far faster than a cold search. Signature: find_proteins(gene=, organism_taxon=, reviewed=, keyword=, ec_number=, mnemonic=, name_contains=, limit=, offset=).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
geneNoGene symbol, e.g. BRCA1.
organism_taxonNoNCBI taxon id, e.g. 9606 for human.
reviewedNoTrue = Swiss-Prot only; False = TrEMBL only.
keywordNoUniProt keyword (KW-id like KW-0007, or a label).
ec_numberNoEC number, e.g. 2.7.11.1.
mnemonicNoEntry mnemonic, e.g. BRCA1_HUMAN.
name_containsNoWords to match in the recommended protein name. Multi-word input matches per word (each word must appear, in any order), so 'polynucleotide kinase' matches 'Bifunctional polynucleotide phosphatase/kinase'. Case-insensitive.
limitNoMax results per page.
offsetNoPagination offset.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
successNo
_metaNo
error_codeNo
messageNo
retryableNo
recovery_actionNo
fieldNo
allowed_valuesNo
hintNo
countNo
proteinsNo
truncatedNo
reviewed_countNo
reviewed_hintNo
Behavior5/5

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

The description adds performance details (cold search vs cached) and result ordering beyond what annotations provide, with no contradictions.

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

Conciseness5/5

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

The description is dense but every sentence serves a purpose, front-loading the main action and then detailing requirements, behavior, and alternatives.

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?

Given parameters, output schema presence, and sibling tools, the description covers all necessary context: use cases, prerequisites, behavior, performance, and relationships.

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?

With 100% schema coverage, the description still adds significant value by explaining constraint logic (e.g., name_contains matches per word), providing examples, and listing required anchors.

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 clearly states the tool searches UniProtKB with structured filters, lists the return fields, and distinguishes from sibling tools like search_example_queries, run_sparql_query, and get_protein.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly states prerequisites (at least one anchor), provides detailed alternatives for different use cases (broad text or known accession), and explains ordering and caching behavior.

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/berntpopp/uniprot-link'

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