Skip to main content
Glama
musharna

plant-genomics-mcp

by musharna

Synthesis: Gene Report (Markdown dossier)

gene_report
Read-onlyIdempotent

Generate a one-shot gene dossier for a plant locus, synthesizing cross-references, KEGG pathways, STRING interactors, Europe PMC literature, and QuickGO GO terms into a Markdown report.

Instructions

Synthesis: one-shot 'tell me about this gene' dossier. Resolves a locus through Ensembl Plants + UniProt, then fans out to cross-references, KEGG pathways, STRING interactors, Europe PMC literature, and QuickGO GO terms. Returns a SynthesisEnvelope whose result.markdown is a rendered Markdown gene dossier (the headline output) alongside a structured result.sections mirror. Any single backend failure degrades that section to an 'Unavailable' note; the rest of the dossier still renders.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
locusYesLocus name, e.g. AT1G01010
top_nNoCaps GO terms, pathways, interactors, xrefs, and papers per section
organismNoPlant organism — accepts canonical slug (arabidopsis_thaliana), scientific or common name, or NCBI taxidarabidopsis_thaliana

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
toolYesSynthesis tool name, e.g. analyze_locus_synth
inputYesEchoed input arguments
stepsYesPer-backend execution rows
resultNoComposed cross-source result; None if root step failed
elapsed_sYesTotal orchestrator wall time
started_atYesISO 8601 UTC timestamp
Behavior5/5

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

Beyond the annotations (read-only, idempotent, open world), the description discloses the crucial failure-isolation behavior: any single backend failure degrades only that section to 'Unavailable' while the rest still renders. It also explains the return envelope structure (result.markdown headline + sections mirror), adding real behavioral context beyond the schema.

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?

Three sentences, front-loaded with the essential ('Synthesis: one-shot...'); every clause earns its place by explaining scope, fan-out sources, output format, and failure behavior. No redundancy or filler.

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?

For a complex multi-source synthesis tool, the description covers inputs (locus resolution), processing (fan-out list), outputs (Markdown + sections), and failure semantics. With a rich schema and output schema present, this is complete enough for an agent to select and invoke it correctly.

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 description coverage is 100%, so the schema already documents all three parameters. The description references 'locus' in passing but adds no additional semantic detail about top_n or organism; per the baseline, a 3 is appropriate.

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 identifies this as a one-shot gene dossier synthesis tool with a specific verb ('tell me about this gene') and resource scope, distinct from sibling tools that query individual data sources. It enumerates the fan-out targets (Ensembl Plants, UniProt, KEGG, STRING, Europe PMC, QuickGO) and the headline output, making the purpose unambiguous.

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 'Synthesis:' prefix and 'one-shot' phrasing make the intended use case clear: get a comprehensive overview of a gene instead of calling individual locus tools. It does not explicitly name alternatives or exclusions, but the dossier framing differentiates it from the granular sibling tools.

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