Skip to main content
Glama

gene_neighbourhood

Read-onlyIdempotent

Gene neighbourhood (microsynteny): the gene and its flanking genes, with their orthologues in related genomes (wheat homoeologues, Ae. tauschii, durum, barley, Brachypodium, rice) from Ensembl Compara. For each target genome, the collinear block holding most orthologues of the neighbourhood is reported with how many neighbours are conserved there, so a candidate gene can be checked for a conserved genomic context. flank: genes each side (default 8, max 25). targets: Ensembl genome names (default ['aegilops_tauschii', 'triticum_turgidum', 'hordeum_vulgare', 'brachypodium_distachyon', 'oryza_sativa']).

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

Input Schema

NameRequiredDescriptionDefault
geneYes
flankNo
targetsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / targets / anyOf
      Previous value: -[
      -  {
      -    "items": {
      -      "type": "string"
      -    },
      -    "type": "array"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "items": {
      +      "type": "string"
      +    },
      +    "type": "array"
      +  },
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
  2. Added

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so safety is covered; the description adds the reporting logic (the collinear block holding most orthologues, with a count of conserved neighbours) and the flank cap of 25, which is genuine beyond-schema context. It stops short of behavioural detail like latency, failure modes when a genome lacks the gene, or what happens on partial hits across the five target genomes.

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?

One front-loaded block that leads with purpose before parameters and the use case; every clause adds information. It is dense but not padded, though the default genome list and the parenthetical genome names in the opening sentence partially duplicate each other.

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?

There is no output schema, and the description does describe the returned structure (per-genome collinear block plus conserved-neighbour count), which covers the main need. It still leaves unclear the shape of individual gene records, ordering, and behaviour when no conserved block is found, so an agent cannot fully anticipate the response.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description carries the burden, and it does explain 'flank' (genes each side, default 8, max 25) and 'targets' (Ensembl genome names, with the default list). The 'gene' parameter is left as common-sense terminology, and the prose mentions wheat homoeologues that are not in the default targets list, a small ambiguity, but overall it compensates well for the empty schema.

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?

States a specific verb and resource ('Gene neighbourhood (microsynteny): the gene and its flanking genes, with their orthologues') and distinguishes itself from siblings such as genes_in_region or gene_function by naming the comparative-genomics data source (Ensembl Compara) and the compared genomes. An agent can identify this as a synteny/context lookup without opening the schema.

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?

Provides a concrete use case — 'so a candidate gene can be checked for a conserved genomic context' — which tells the agent when this tool is the right choice rather than a plain annotation or region lookup. It does not name an explicit alternative or state when not to use it, leaving the routing to the agent.

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