Skip to main content
Glama
musharna

plant-genomics-mcp

tair_locus_info

Retrieve TAIR curator summary, Araport11 description, NCBI Gene ID, and cross-DB aliases for Arabidopsis loci, bypassing paid subscriptions.

Instructions

Fetch the TAIR curator-vetted Arabidopsis locus summary. Served via BAR/ThaleMine (U Toronto, Global Core Biodata Resource 2023) since TAIR's free per-locus REST API is gated behind a paid Phoenix Bioinformatics subscription. Returns TAIR curator summary + Araport11 computational description + NCBI Gene ID + cross-DB aliases (RefSeq, UniProt, TIGR locus-model IDs). Arabidopsis only. Alias of bar_gene_summary.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
locusYesArabidopsis AGI locus, e.g. AT1G01010

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
locusYes
agiNoAGI primary identifier echoed by ThaleMine, e.g. "AT1G01010"
symbolNoGene symbol, e.g. "NAC001"
full_nameNoGene name from ThaleMine
tair_locus_idNoTAIR locus ID from Gene.secondaryIdentifier, e.g. "locus:2200935"
synonymsNoTAIR aliases (CSV from Gene.tairAliases, split on commas + stripped)
computational_descriptionNoGene.tairComputationalDescription — Araport11-sourced computed description
curator_summaryNoGene.tairCuratorSummary — the TAIR-curated functional summary prose
brief_descriptionNoGene.briefDescription — short blurb (often same as full_name)
tair_short_descriptionNoGene.tairShortDescription — TAIR-specific short description
ncbi_gene_idNoNCBI Gene ID from /gaia/aliases/ — None if BAR has no NCBI cross-ref
aliasesNoCross-DB aliases from /gaia/aliases/ (RefSeq accessions, UniProt accessions, TIGR locus-model IDs, and TAIR aliases). Empty list if /gaia degraded.
speciesYes
source_urlYesThaleMine endpoint URL for traceability
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It discloses the output contents (curator summary, Araport11 description, NCBI ID, cross-DB aliases) and the data source, but does not discuss potential rate limits, permissions, or side effects; however, 'Fetch' implies a read-only operation.

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 concise, conveying all necessary information in a few sentences without redundancy. It front-loads the main action and follows with relevant context and disambiguation.

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 has an output schema (not shown but indicated), the description sufficiently explains what the output contains. It covers the tool's purpose, data source, constraints ('Arabidopsis only'), and relationship to sibling tools, making it complete for an agent to use correctly.

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 schema already describes the parameter as an AGI locus. The description adds an example ('AT1G01010') and context about the locus format, which enhances understanding beyond the schema.

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 specifies a specific verb ('Fetch') and resource ('TAIR curator-vetted Arabidopsis locus summary'), clearly distinguishing it from siblings by noting it is an alias of bar_gene_summary and explaining its origin from BAR/ThaleMine as an alternative to a paid API.

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 states 'Arabidopsis only' and explains why this tool exists (bypassing paid TAIR API), but does not explicitly mention when not to use it or recommend alternatives among the many siblings listed, though the alias note hints at equivalence with bar_gene_summary.

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