Skip to main content
Glama
musharna

plant-genomics-mcp

resolve_locus_to_uniprot

Resolve a plant gene locus to its canonical UniProtKB protein record, prioritizing curated Swiss-Prot entries.

Instructions

Resolve a plant locus to its canonical UniProtKB record. Prefers reviewed (Swiss-Prot) entries; falls back to unreviewed (TrEMBL) when no curated record exists (common for non-Arabidopsis plants). organism accepts a canonical slug, scientific/common name, or NCBI taxid (default arabidopsis_thaliana; e.g. oryza_sativa, zea_mays). Returns primaryAccession, uniProtkbId, entryType, recommendedName, geneNames, organism, taxonId, sequenceLength, web_url. This is the protein-side entry point — pair with InterPro / AlphaFold / Reactome / structural-bio tools.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
locusYese.g. AT1G01010 (Arabidopsis), Os01g0100100 (rice)
organismNoPlant organism — accepts canonical slug (arabidopsis_thaliana), scientific or common name, or NCBI taxidarabidopsis_thaliana

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
locus_queryYesThe locus identifier the user asked about
primaryAccessionYesUniProt accession, e.g. Q0WV96
uniProtkbIdYesUniProtKB ID, e.g. NAC1_ARATH
entryTypeYese.g. 'UniProtKB reviewed (Swiss-Prot)' or '... (TrEMBL)'
reviewedYesTrue if Swiss-Prot (curated)
recommendedNameNoRecommended protein name
geneNamesNoGene symbols, e.g. ['NAC001']
organismNoScientific name
taxonIdNoNCBI taxonomy ID
sequenceLengthNoProtein length in residues
web_urlNoBrowser URL for the UniProt entry
Behavior4/5

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

No annotations exist, so description carries full burden. It reveals preference for Swiss-Prot, fallback to TrEMBL, and lists returned fields. Missing details on error handling or rate limits, but covers key behavioral aspects.

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 mostly concise with two main sentences, but the list of returned fields adds verbosity. Still, it remains well-structured and front-loaded with the core purpose.

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 the tool's moderate complexity and presence of output schema, the description is fully adequate. It covers input, output, fallback behavior, organism flexibility, and contextual pairing with sibling tools.

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?

Despite 100% schema coverage, description adds significant value: explains locus format with examples (AT1G01010, Os01g0100100) and describes organism parameter acceptance (slug, name, taxid) with default and examples.

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 it resolves a plant locus to UniProtKB, specifying verb and resource. It distinguishes itself as the 'protein-side entry point' from sibling tools like atted_coexpression or gramene_homologs.

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?

The description explains when to use this tool (protein mapping) and suggests pairing with InterPro/AlphaFold tools. It also details fallback behavior and organism parameter usage, but does not explicitly state when not to use it.

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/musharna/plant-genomics-mcp'

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