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. 'medicago_truncatula' or 'pisum_sativum'). 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

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds the return contract (orthologue IDs, species, relationship types one2one/one2many/many2many), which is genuinely useful given no output schema, but says nothing about empty results or cross-species coverage limits beyond the source name.

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?

Two dense sentences front-loaded with purpose, then parameter hints, then return values; little waste. The parenthetical 'gene trees across plant genomes' is slight filler but adds a little interpretive context.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema the description wisely specifies return fields, which is a significant completion. However, it omits the 'species' parameter and any handling of null defaults or multi-species queries, so an agent could still be unsure how to call it with all three arguments.

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 must compensate. It explains gene format ('Ensembl ID or name') and target_species with concrete examples, but leaves the third parameter, 'species', completely unmentioned, leaving a real gap in a three-parameter tool.

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 verb and resource ('Orthologues of a gene') plus the data source (Ensembl Plants Compara) and a concrete example ('the Brassica copies of an Arabidopsis gene'). It does not explicitly contrast with siblings like find_gene or legume_gene, so it stops short of full sibling differentiation.

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 mention of target_species to 'restrict to' one species implies a filtering use case, and the example suggests when the tool fits. But there is no explicit when-to-use vs when-not, no guidance on choosing between this and gene-centric siblings, and no prerequisites (e.g., gene must exist in Ensembl Plants).

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