Skip to main content
Glama

gene_neighbourhood

Read-onlyIdempotent

Gene neighbourhood (microsynteny): the gene and its flanking genes, with their orthologues in related genomes (pea, faba bean, Medicago, soybean, common bean, lupin) 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 ['pisum_sativum', 'vicia_faba', 'medicago_truncatula', 'glycine_max', 'phaseolus_vulgaris', 'lupinus_angustifolius']).

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

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds real value by explaining what is reported for each target genome (the collinear block holding most orthologues plus the count of conserved neighbours), but it says nothing about failure modes, cost, or runtime for a multi-genome comparison.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core purpose is front-loaded, which is good, but the middle sentence about collinear blocks is dense and the parameter notes are appended as terse fragments rather than structured guidance. It is informative without much padding, yet the run-on framing makes it slower to parse than it needs to be.

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 does the right thing by describing the return concept (collinear block plus conserved-neighbour count) and by documenting defaults and the max flank. It remains incomplete on identifier format, single-vs-list target input, and behavior when a target genome has no syntenic block, which matters for a three-parameter cross-genome tool.

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 0%, so the description must carry the load: it does explain 'flank: genes each side (default 8, max 25)' and 'targets: Ensembl genome names' with the full default list, which is the most useful compensation possible here. However, it does not clarify whether targets accepts a single string versus a list (the schema uses anyOf) or what the gene identifier format should be.

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?

The description opens with a specific verb-and-resource statement ('Gene neighbourhood (microsynteny): the gene and its flanking genes') and specifies the orthologue source (Ensembl Compara) and target genomes. It is clearly distinct in scope from a plain orthologue lookup, though it never names a sibling tool to contrast with, so an agent must infer the boundary itself.

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?

Usage is only implied through the closing rationale ('so a candidate gene can be checked for a conserved genomic context'), which is a genuine use case but not an explicit when-to-use rule. There is no guidance on when to prefer this over the orthologues tool or what to do when no conserved block is found.

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