Skip to main content
Glama
musharna

plant-genomics-mcp

tair_locus_info

Fetch the TAIR curator-vetted Arabidopsis locus summary, including functional description and cross-database identifiers, from a free public resource.

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
Behavior3/5

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

No annotations provided. The description discloses the returned data types (curator summary, Araport11 description, NCBI Gene ID, aliases) and data source. But it does not mention error behavior, rate limits, or any side effects. For a read-only fetch, this is acceptable but could be more transparent.

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 packing essential information (purpose, data source, reason, content, restrictions, alias). No filler, front-loaded with main action.

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?

With an output schema present, the description adequately covers what the tool does and what it returns. It is missing some behavioral aspects but is sufficient for a simple query tool. The alias note adds clarity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, the schema already describes the 'locus' parameter as an AGI locus with example. The description adds no further semantics beyond what the schema provides, so baseline score applies.

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?

Clearly states it fetches a TAIR curator-vetted Arabidopsis locus summary. The verb 'Fetch' is specific, the resource is named (TAIR/ThaleMine), and it distinguishes from the paid TAIR API and identifies itself as an alias of bar_gene_summary.

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?

Provides context for when to use: because TAIR's free REST API is gated behind a paid subscription. Specifies it is Arabidopsis only. However, it does not differentiate from its alias bar_gene_summary, which may cause confusion; but the explanation of the tool's rationale partially compensates.

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