Skip to main content
Glama
musharna

plant-genomics-mcp

locus_go_annotations

Fetch Gene Ontology annotations for any plant locus from QuickGO. Resolves locus to UniProt accession and returns GO terms grouped by molecular function, biological process, and cellular component.

Instructions

Fetch Gene Ontology annotations for a plant locus from QuickGO (EBI). Free, no API key. The locus is first resolved to a UniProt accession via the same logic as resolve_locus_to_uniprot, then QuickGO is queried by geneProductId. Returns annotations[] with goId/goName/goAspect/qualifier/evidence + a by_aspect rollup ({molecular_function: [{goId, goName}, ...], biological_process: [...], cellular_component: [...]}) deduped on goId so the high-level term set is one read away.

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
limitNoMax annotations from QuickGO (1–100, default 50)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
locusYes
uniprot_accessionYesUniProt accession used to query QuickGO
numberOfHitsYesTotal annotations available upstream
returnedYesNumber of annotations in annotations[]
annotationsYes
by_aspectYesaspect → [{goId, goName}, ...], deduped on goId
Behavior5/5

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

Fully transparent: explains internal resolution to UniProt, querying QuickGO by geneProductId, output format with dedup on goId, and rollup by aspect. Notes that it's free and no API key. No annotations exist, so the description carries the full burden and meets it.

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?

Two sentences, front-loaded with the main action, then details. Every sentence adds value with no redundancy.

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?

Correctly describes the tool's behavior, parameters, and output structure. The output schema exists but the description already details the return format, making it complete for an agent to invoke correctly.

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. The description adds value by explaining the resolution of 'locus' to UniProt, the flexible 'organism' formats, and the range of 'limit'. This exceeds the schema descriptions.

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?

Clear verb 'Fetch Gene Ontology annotations' plus specific resource 'plant locus from QuickGO'. Distinguishes from sibling tools like 'batch_locus_go_annotations' and 'resolve_locus_to_uniprot' by naming the exact source and output.

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?

Explicitly describes the process and output structure, and mentions the resolution step similar to 'resolve_locus_to_uniprot'. Does not explicitly state when to avoid or compare to alternatives, but provides enough context for correct use.

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