Skip to main content
Glama
musharna

plant-genomics-mcp

by musharna

Ensembl Plants: Paralogs

ensembl_plants_paralogs
Read-onlyIdempotent

Find paralogues of a plant locus using Ensembl Compara, returning duplication type, taxonomy level, and percent identity to reveal evolutionary relationships.

Instructions

List the paralogues Ensembl Compara (plants) records for a plant locus (rest.ensembl.org /homology, type=paralogues; free, no key). Each row gives the paralogue's locus, its type — within_species_paralog, or other_paralog: Ensembl's 'ancient paralogues', inferred across a super tree, so the two genes can sit in different gene trees — the taxonomy_level of the duplication, perc_id/perc_pos and protein_id, closest first. gramene_homologs carries only within_species_paralog, so a gene can have paralogues here and none there. A paralogue list is not a family list: other_paralog can name a gene outside the family (AT2G23390, an acyl-CoA N-acyltransferase-like gene, is an other_paralog of the ARFs); test membership with interpro_domains. An empty list means Compara records no paralogue, not that the gene is single-copy (FLS2, AT5G46330, has none). found=false when Compara keeps no homology record for the gene at all (e.g. a non-coding gene); an id Ensembl does not know is a not-found error. total and counts_by_type count before limit; truncated=true when limit cut some off.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
locusYese.g. AT1G19850 (Arabidopsis), Os04g0519700 (rice)
organismNoPlant organism — accepts canonical slug (arabidopsis_thaliana), scientific or common name, or NCBI taxidarabidopsis_thaliana

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
foundYesFalse when Compara keeps no homology record for this gene at all (e.g. a non-coding gene); true otherwise, even with no paralogue
locusYesThe locus asked about
totalYesHow many paralogues exist upstream for this query, all pages (pre-cap) (#123)
organismYesCanonical organism slug
paralogsYesClosest first (perc_id descending)
returnedYesRows in this payload (#123)
truncatedYesTrue when limit cut paralogues off
counts_by_typeYesParalogues per type, counted before limit
upstream_versionNoEnsembl release that produced THIS response, — always null today: this backend states no release on its responses; upstream_release(backend='ensembl_plants') reports the release its own endpoint calls current at query time, or why there is none. null means Ensembl did not state one — never that no release exists, and never inferred from a separate metadata call, which can describe a different release than the one that answered.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.27.0
    • changedOutput schema / properties / upstream_version / description
      Previous value: -"Ensembl release that produced THIS response, — always null today: this backend states no release on its responses. null means Ensembl did not state one — never that no release exists, and never inferred from a separate metadata call, which can describe a different release than the one that answered."New value: +"Ensembl release that produced THIS response, — always null today: this backend states no release on its responses; upstream_release(backend='ensembl_plants') reports the release its own endpoint calls current at query time, or why there is none. null means Ensembl did not state one — never that no release exists, and never inferred from a separate metadata call, which can describe a different release than the one that answered."
  2. Addedv1.26.0

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations (readOnly, idempotent, openWorld), the description explains output row fields (locus, type, taxonomy_level, perc_id/perc_pos, protein_id), the differences between within_species_paralog and other_paralog, and the pagination behavior (total and counts_by_type before limit, truncated=true). It also warns that a paralogue list is not a family list, which is a subtle non-obvious behavior. This adds substantial context without contradicting the annotations.

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 long but each sentence serves a purpose: explaining output fields, contrasting with gramene_homologs, clarifying edge cases, and describing pagination. The core purpose is front-loaded in the first sentence, and the detailed examples (AT2G23390, FLS2) justify the length. It could be slightly tighter, but the density is appropriate given the tool's complexity.

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?

The description covers all non-obvious aspects of the tool: paralogue types, the distinction between empty list and found=false, unknown ID errors, and limit truncation. With an output schema present for return structure, the agent has everything needed to call and interpret the tool. No critical gaps remain for a wrapper around an external API.

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 67%, so locus and organism are already documented in the schema. The description does not add any semantic detail about these parameters, and only indirectly hints at the limit parameter through 'truncated=true when limit cut some off.' This is minimal added value; it could have explicitly described the limit's purpose and the organism's accepted formats.

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 opens with a clear verb and resource: 'List the paralogues Ensembl Compara (plants) records for a plant locus.' It also specifies the underlying API endpoint (rest.ensembl.org /homology, type=paralogues), which unambiguously identifies the tool's function. It further differentiates from sibling gramene_homologs by noting the difference in paralogue types.

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 contrasts this tool with gramene_homologs, noting that a gene can have paralogues here but none there, and advises using interpro_domains to test family membership. It also clarifies critical semantics: an empty list means Compara records no paralogue, found=false means no homology record, and a not-found error for unknown IDs. This gives an agent clear guidance on when to use this tool versus alternatives.

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