Skip to main content
Glama
plant-genomics-mcp

plant-genomics-mcp

by musharna

Synthesis: Consensus Homologs

consensus_homologs
Read-onlyIdempotent

Combines Gramene homology and NCBI BLAST results for a plant locus, deduplicates candidate loci, and ranks hits by cross-source support and mean identity.

Instructions

Synthesis: cross-source homology consensus. Resolves UniProt + FASTA sequence, then runs Gramene homology calls and NCBI BLAST in parallel. Dedupes hits by normalized locus token and scores by n_sources * mean_identity — Gramene contributes identity=1.0, BLAST contributes pident/100.

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": "consensus_homologs"
  }
}

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. Addedv1.21.0
  4. Removedv1.20.0
  5. 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 cover the read-only, idempotent, open-world safety profile, and the description goes well beyond them: it discloses internal pipeline steps (resolution, parallel calls), the dedupe key, and the exact scoring formula including Gramene's fixed identity=1.0. It omits failure handling when one source errors, latency implications of parallel external calls, and any rate-limit constraints.

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 dense sentences, front-loaded with purpose then mechanism then scoring, with no filler; the 'Synthesis:' prefix and every clause add information the agent needs.

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-format explanation is unnecessary, and the scoring formula plus source weighting is a strong completion of the agent's mental model for a composite tool. What's missing is operational: behavior when one of the parallel sources fails, and the meaning of top_n in the consensus ranking.

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% (organism alone is described), so the description must carry weight; 'normalized locus token' hints at accepted locus formats and 'scores by...' implies ranking, but top_n is never explained — no statement that it truncates the ranked consensus list, nor how ties are broken. Partial compensation only.

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?

States a specific operation — 'cross-source homology consensus' — and explains the mechanism (UniProt/FASTA resolution plus parallel Gramene + BLAST calls). Combined with the scoring formula, an agent can distinguish this composite tool from single-source siblings like gramene_homologs or blast_sequence, though no sibling is named explicitly.

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 described pipeline (both sources, consensus scoring) implies this is the tool for cross-source agreement rather than single-source lookups, but the description never states when to prefer it over gramene_homologs, find_homologs_synth, or blast_sequence, nor any exclusions or cost trade-offs.

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