Skip to main content
Glama

orthologues

Read-onlyIdempotent

Orthologues of a gene from Ensembl Plants Compara (gene trees across plant genomes), e.g. the Brassica copies of an Arabidopsis gene. gene: Ensembl ID or name; target_species: Ensembl name to restrict to (e.g. 'brassica_napus'). Returns orthologue IDs, species, relationship (one2one, one2many, many2many).

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": {
      "gene": "<gene>"
    },
    "name": "orthologues"
  }
}

Input Schema

NameRequiredDescriptionDefault
geneYes
speciesNo
target_speciesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds real behavioral context beyond that: the underlying data source (Ensembl Plants Compara gene trees) and the shape of the result (orthologue IDs, species, and relationship type such as one2one/one2many/many2many). It says nothing about result volume or pagination, but for a read-only lookup that is minor.

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?

Three tight sentences: purpose first, then parameter glosses, then return shape. No filler. The semicolon-chained fragments are slightly dense but everything present earns its place.

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?

For a three-parameter read-only tool with no output schema, the description covers the operation, the data source, parameter formats, and the returned fields. The only meaningful hole is the unexplained 'species' parameter relative to 'target_species'.

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 0%, so the description has to carry parameter meaning, and it does explain gene (Ensembl ID or name) and target_species (Ensembl species name, e.g. 'brassica_napus'). However, the third parameter 'species' is never mentioned, leaving its distinction from target_species — a genuine ambiguity — unresolved for the agent.

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?

Names a concrete resource and scope: orthologues of a gene from Ensembl Plants Compara, with a concrete example ('Brassica copies of an Arabidopsis gene'). It is clearly distinguishable from sibling gene-lookup tools by the Compara gene-tree framing, though no sibling is named outright.

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 Arabidopsis/Brassica example gives a clear picture of when this tool is the right choice, and target_species is framed as an optional narrowing filter. There is no explicit statement of when NOT to use it or which sibling to pick instead for other comparative queries.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources