Skip to main content
Glama
musharna

plant-genomics-mcp

ensembl_plants_lookup_locus

Retrieve plant gene metadata for a TAIR-style locus from Ensembl Plants; specify the organism for species like rice or maize.

Instructions

Fetch metadata for a plant locus identifier from Ensembl Plants. Defaults to arabidopsis_thaliana; pass organism= for other plant species (oryza_sativa, zea_mays, ...). Locus is the TAIR-style identifier (e.g. AT1G01010 for Arabidopsis NAC001).

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
idYesLocus identifier, e.g. AT1G01010
organismYesPlant organism canonical slug, e.g. arabidopsis_thaliana
object_typeNoUsually "Gene"
biotypeNoprotein_coding, lncRNA, miRNA, ...
display_nameNoHuman-readable gene symbol
descriptionNo
seq_region_nameNoChromosome / contig name
startNo
endNo
strandNo1 forward, -1 reverse
assembly_nameNoe.g. TAIR10
db_typeNoUsually "core"
logic_nameNoSource annotation pipeline
sourceNo
canonical_transcriptNo
Behavior2/5

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

With no annotations provided, the description must fully disclose behavioral traits. It only states it fetches metadata, without mentioning that it is a read-only operation, potential errors, rate limits, or any side effects.

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 two sentences, front-loaded with the verb and resource, and contains no superfluous information. Every sentence adds value.

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?

Given the tool has only 2 parameters, no nested objects, and an output schema exists, the description covers the main aspects adequately. It does not explain the output format, but that may be covered by the output schema.

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?

The input schema has 100% coverage, so baseline is 3. The description adds value by clarifying the locus format (TAIR-style) with examples, and specifying the default organism for the 'organism' parameter.

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?

The description states it fetches metadata for a plant locus identifier from Ensembl Plants, with a default organism and examples. However, it does not explicitly differentiate from sibling tools such as phytozome_lookup_locus or tair_locus_info, which also perform similar lookups.

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

Usage Guidelines3/5

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

The description implies usage by specifying the default organism and providing examples of locus identifiers, but it does not provide explicit guidance on when to use this tool versus alternatives like phytozome_lookup_locus or batch_ensembl_plants_lookup_locus.

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