Skip to main content
Glama
musharna

plant-genomics-mcp

by musharna

Resolve Locus → UniProt

resolve_locus_to_uniprot
Read-onlyIdempotent

Resolve a plant locus (e.g., AT1G01010) to its UniProtKB protein record. Preferences Swiss-Prot; falls back to TrEMBL if unavailable. Returns accession, names, gene details, organism, and sequence length.

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
taxonIdNoNCBI taxonomy ID
web_urlNoBrowser URL for the UniProt entry
organismNoScientific name
reviewedYesTrue if Swiss-Prot (curated)
entryTypeYese.g. 'UniProtKB reviewed (Swiss-Prot)' or '... (TrEMBL)'
geneNamesNoGene symbols, e.g. ['NAC001']
locus_queryYesThe locus identifier the user asked about
uniProtkbIdYesUniProtKB ID, e.g. NAC1_ARATH
sequenceLengthNoProtein length in residues
recommendedNameNoRecommended protein name
primaryAccessionYesUniProt accession, e.g. Q0WV96
upstream_versionNoUniProt release that produced THIS record, as stated by the upstream's own header (e.g. '2026_02'). null means UniProt did not state one — never that no release exists, and never inferred from a separate metadata call, which can describe a different release than the one that answered.
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint false, conveying safety. The description adds critical behavioral detail: it prefers Swiss-Prot and falls back to TrEMBL, which is beyond annotation scope.

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 well-structured with a clear first sentence, followed by details. It is not overly verbose, though the return field list could be moved to the output schema. Every sentence is informative.

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 simplicity (2 params, clear schema, output schema exists, annotations cover safety), the description covers purpose, usage, parameter details, fallback logic, and pairing guidance. It is comprehensive.

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% with descriptions for both parameters, so baseline is 3. The description adds value by explicitly listing accepted formats for organism (slug, name, taxid) and providing examples, enhancing understanding.

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 its canonical UniProtKB record, specifying the verb, resource, and scope. It differentiates from siblings by calling it the 'protein-side entry point' and listing paired tools.

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 advises pairing with InterPro, AlphaFold, etc., indicating when to use this tool. However, it does not explicitly contrast with alternative locus tools or state when not to use it, leaving some ambiguity.

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