Skip to main content
Glama
musharna

plant-genomics-mcp

by musharna

TAIR-Style Locus Summary

tair_locus_info
Read-onlyIdempotent

Retrieve curator-vetted summary and cross-database aliases for Arabidopsis loci, bypassing the paid TAIR API using BAR/ThaleMine data.

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
agiNoAGI primary identifier echoed by ThaleMine, e.g. "AT1G01010"
locusYes
symbolNoGene symbol, e.g. "NAC001"
aliasesNoCross-DB aliases from /gaia/aliases/ (RefSeq accessions, UniProt accessions, TIGR locus-model IDs, and TAIR aliases). Empty list if /gaia degraded.
speciesYes
synonymsNoTAIR aliases (CSV from Gene.tairAliases, split on commas + stripped)
full_nameNoGene name from ThaleMine
source_urlYesThaleMine endpoint URL for traceability
ncbi_gene_idNoNCBI Gene ID from /gaia/aliases/ — None if BAR has no NCBI cross-ref
tair_locus_idNoTAIR locus ID from Gene.secondaryIdentifier, e.g. "locus:2200935"
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
computational_descriptionNoGene.tairComputationalDescription — Araport11-sourced computed description
Behavior5/5

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

Annotations already provide idempotent, read-only, non-destructive hints. The description adds valuable behavioral details: it returns curator summary, computational description, NCBI Gene ID, and cross-database aliases, and identifies the data source. No contradictions.

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 compact and front-loaded, conveying essential information in two sentences with no redundancy. Every sentence adds value.

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 presence of an output schema (not shown), the description appropriately omits return value details. It covers purpose, source, scope, and relationship to siblings, which is complete for a single-parameter tool.

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% for the single 'locus' parameter, with a descriptive example. The description adds the Arabidopsis-only restriction, which provides semantic context beyond the schema. This justifies a score above the baseline of 3.

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 the tool fetches a TAIR curator-vetted Arabidopsis locus summary. It specifies the resource (BAR/ThaleMine) and distinguishes itself from siblings by mentioning it's an alias of bar_gene_summary and restricted to Arabidopsis.

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

Usage Guidelines5/5

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

The description explicitly states when to use the tool (for TAIR-style curator summaries), notes it is specific to Arabidopsis, and provides context that it replaces a paid TAIR API. The alias reference clarifies its relationship to 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