Skip to main content
Glama
musharna

plant-genomics-mcp

bar_gene_summary

Retrieve a merged gene summary for an Arabidopsis locus from BAR, including curator summary, computational description, NCBI ID, and cross-database aliases.

Instructions

Fetch the BAR (Bio-Analytic Resource, U Toronto) merged ThaleMine + GAIA-aliases summary for an Arabidopsis locus. Returns the TAIR curator summary + Araport11 computational description from /thalemine/gene_information/ together with the NCBI Gene ID and cross-DB aliases (RefSeq, UniProt, TIGR locus-model IDs) from /gaia/aliases/. Arabidopsis only — ThaleMine carries taxon 3702 plus yeast/human for ortholog cross-reference. BAR is keyless and a Global Core Biodata Resource (2023); replaces the v0.9 subscription-gated tair_locus_info stub for the curator-summary use case.

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?

With no annotations provided, the description carries the full burden and details that the tool is keyless, fetches from two endpoints, and returns a specific set of data. It does not disclose error handling or rate limits, but the behavioral context is reasonably transparent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise yet comprehensive, front-loading the purpose and then providing context. It is a single paragraph with no wasted sentences, though it could be slightly shorter.

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's complexity (two data sources, specific output), the description explains the logic, data origin, and replacement context. An output schema exists, so return values are covered externally. It is slightly incomplete on error handling but otherwise thorough.

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?

The schema already describes the single parameter 'locus' with an example. The description adds only that it is Arabidopsis-specific, which is a minor enhancement. With 100% schema coverage, the baseline is 3 and the description does not significantly add 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 clearly states the tool fetches a merged summary from ThaleMine and GAIA-aliases for an Arabidopsis locus, specifying the exact data sources and outputs. It distinguishes itself from the sibling 'tair_locus_info' by noting it replaces that stub for the curator-summary use case.

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 limits usage to Arabidopsis loci and notes the tool is a replacement for the old subscription-gated tair_locus_info, providing clear context. However, it does not explicitly compare to other sibling tools or state when not to use it.

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