Skip to main content
Glama
plant-genomics-mcp

plant-genomics-mcp

by musharna

Synthesis: Biological Context

biological_context_synth
Read-onlyIdempotent

Resolve a plant locus to its UniProt accession and gather homologs, KEGG pathways, STRING partners, and ATTED-II coexpression in one call, with a merged consensus partner ranking.

Instructions

Synthesis: one-call equivalent of the biological_context prompt. Resolves UniProt accession, then fans out to Gramene homologs, KEGG pathways, STRING-DB partners, and ATTED-II coexpression in parallel. Adds a consensus_partners ranking that merges STRING + ATTED scores.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "locus": "<locus>"
    },
    "name": "biological_context_synth"
  }
}

Input Schema

NameRequiredDescriptionDefault
locusYes
top_nNo
organismNoPlant organism — accepts canonical slug (arabidopsis_thaliana), scientific or common name, or NCBI taxidarabidopsis_thaliana

Output 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
failed_stepsNoStep numbers whose status is "error". Non-empty means the result is partial: the call succeeded, so it is not an error result, but these backends failed and their sections are missing; each step's error says why.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.31.0
    • addedOutput schema / properties / failed_steps
      Added value: +{
      +  "description": "Step numbers whose status is \"error\". Non-empty means the result is partial: the call succeeded, so it is not an error result, but these backends failed and their sections are missing; each step's error says why.",
      +  "items": {
      +    "type": "integer"
      +  },
      +  "title": "Failed Steps",
      +  "type": "array"
      +}
  2. Changed2 schema fields changedv1.22.0
    • changedOutput schema / $defs / StepRow / description
      Previous value: -"One backend call inside a synthesis envelope.\n\n``status=\"ok\"`` populates ``result``; ``status=\"error\"`` populates ``error``\nwith the existing ``[ExceptionClass] message`` wire format from\n``errors.PlantGenomicsError.__str__``. ``status=\"skipped\"`` populates\n``error`` with a human-readable skip reason (e.g. phase 1 failed)."New value: +"One backend call inside a synthesis envelope.\n\n``status=\"ok\"`` populates ``result`` — unless the orchestrator carries the\npayload elsewhere in the envelope (``gene_report`` keeps it once, under\n``result.sections``), in which case the row is the audit trail alone and\n``result`` is None. ``status=\"error\"`` populates ``error`` with the\nexisting ``[ExceptionClass] message`` wire format from\n``errors.PlantGenomicsError.__str__``. ``status=\"skipped\"`` populates\n``error`` with a human-readable skip reason (e.g. phase 1 failed)."
    • changedOutput schema / $defs / StepRow / properties / elapsed_s / description
      Previous value: -"Per-step wall time when separately measurable, else None. Phase-2 gather rows and phase-0 pre-call validation failures return None because their wall time can't be honestly attributed per-step; SynthesisEnvelope.elapsed_s carries the authoritative total."New value: +"Per-step wall time: every awaited backend call is timed on its own, including inside a phase-2 gather. None only for rows that never ran (skipped, or a phase-0 pre-call validation failure); SynthesisEnvelope.elapsed_s carries the orchestrator total."
  3. First observedv1.8.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so the safety profile is covered. The description adds real behavioral context beyond that: the fan-out happens in parallel and a derived consensus_partners field merges STRING and ATTED scores, telling the agent the output contains synthesized ranking data it would not get from any single source.

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 compact sentences, front-loaded with the identity ('one-call equivalent of the biological_context prompt') and then the pipeline steps in execution order. No filler or restated title boilerplate.

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?

An output schema exists, so return-shape details are rightly omitted, and the annotations cover safety. The remaining gap is the unexplained top_n parameter and the absence of any failure/partial-result guidance for a tool that fans out to four external services, but overall it is sufficient to invoke 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 coverage is only 33%, so the description carries extra burden: it explains that the main input is resolved to a UniProt accession, which clarifies 'locus'. However, top_n is never mentioned despite its default of 10 and maximum of 50, leaving its scope (top partners? top pathways?) ambiguous, and organism only gets meaning from the schema description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb-plus-resource framing: it resolves a UniProt accession and fans out to Gramene homologs, KEGG pathways, STRING-DB partners, and ATTED-II coexpression, then adds a consensus_partners ranking. This makes the tool's aggregate nature clear and implicitly separates it from the single-source siblings (atted_coexpression, find_homologs_synth), though it never names a sibling directly.

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

Usage Guidelines3/5

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

The phrase 'one-call equivalent of the biological_context prompt' implies using this instead of chaining the individual lookups, and 'in parallel' signals the efficiency benefit. There is no explicit when-not guidance (e.g., use a single-source tool when you only need coexpression) and no prerequisites or cost/latency caveats.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.