Skip to main content
Glama

genes_in_region

Read-onlyIdempotent

Genes overlapping a region of one Ensembl Plants genome (max 5 Mb). species is an Ensembl name, e.g. 'pisum_sativum', 'vicia_faba', 'glycine_max' or 'lupinus_angustifolius'; chromosome names as in that assembly. Chromosome names differ by assembly: pea 1LG6..7LG7, narrow-leafed lupin LG01..LG20, soybean 1..20; faba bean uses ENA sequence accessions (e.g. OX451735.1).

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": {
      "species": "<species>",
      "chromosome": "<chromosome>",
      "start": "<start>",
      "end": "<end>"
    },
    "name": "genes_in_region"
  }
}

Input Schema

NameRequiredDescriptionDefault
endYes
limitNo
startYes
speciesYes
chromosomeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, open-world and non-destructive behavior, so the safety profile is covered. The description adds genuinely new behavioral context beyond the annotations: a 5 Mb maximum region size and the fact that chromosome naming is assembly-specific, both of which affect whether a call will succeed.

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 dense sentences, front-loaded with the core operation and the size limit, then the parameter guidance. Every clause carries information; the chromosome enumeration is long but directly actionable, not padding.

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 should say more about what the returned gene records look like, and the coordinate interpretation (0- vs 1-based, start/end ordering) and 'limit' semantics for a 5-parameter required-heavy tool are unaddressed. The species and chromosome guidance is strong, so it is adequate but incomplete for a genomic-range query.

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 carries the burden. It does this well for 'species' (Ensembl name format with concrete examples) and 'chromosome' (per-assembly naming schemes, including ENA accessions for faba bean), but says nothing about 'start', 'end' (coordinate convention, inclusivity) or 'limit' (default 200 or its cap).

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 gives a specific verb and resource ('Genes overlapping a region of one Ensembl Plants genome') plus a hard scope limit (max 5 Mb), so the agent knows exactly what is returned. It does not explicitly contrast itself with the similarly named sibling 'legume_genes_in_region', leaving the single-genome vs multi-genome distinction implicit.

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 implied through constraints ('one Ensembl Plants genome', 'max 5 Mb') rather than stated as when-to-use guidance. There is no explicit instruction on when to prefer this over 'legume_genes_in_region' or 'find_gene', and no exclusions are given.

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