Skip to main content
Glama

gene_neighbourhood

Read-onlyIdempotent

Gene neighbourhood (microsynteny): the gene and its flanking genes, with their orthologues in related genomes (B. napus, B. rapa R-o-18, B. oleracea, Camelina, Arabidopsis) 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 ['brassica_napus', 'brassica_rapa_ro18', 'brassica_oleracea', 'camelina_sativa', 'arabidopsis_thaliana']).

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

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and openWorld, so the safety profile needs no restating. The description adds genuine behavioral context the annotations cannot: the upstream source (Ensembl Compara) and the shape of the result (per target genome, the collinear block holding most orthologues plus a conserved-neighbour count). It does not mention failure modes for unknown genome names or empty results, so it remains additive but not rich.

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?

Purpose and data source are front-loaded, followed by output semantics and then parameter notes — a sensible order with no filler sentences. The middle sentence is long and slightly run-on, but every clause carries information rather than restating the name.

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?

With no output schema and three parameters, the description supplies what an agent needs: what is compared, against which genomes, what the reported block means, and the tunable window size. Missing only edge-case behavior such as what happens when a target genome lacks syntenic context, which is minor for a read-only lookup.

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 description coverage is 0%, so the description carries the full burden and largely meets it. It explains 'flank' as genes each side with default 8 and a max of 25 (the max is not in the schema), and explains 'targets' as Ensembl genome names, listing the default genome set. 'gene' is left implicit but is self-evident from the tool purpose.

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+resource: retrieves the gene plus its flanking genes and their orthologues across five named genomes via Ensembl Compara, and names the key output (the collinear block with conserved-neighbour counts). An agent can tell this is a synteny/context tool rather than a plain orthologue lookup. It stops short of naming the sibling 'orthologues' as the contrasting alternative, so differentiation is implied rather than explicit.

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?

Gives a clear motivating use case: 'so a candidate gene can be checked for a conserved genomic context.' That tells the agent when this tool is appropriate. There are no explicit exclusions or named alternatives (e.g., when to prefer 'orthologues' or 'genes_in_region'), which keeps it below a 5.

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