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. 'brassica_rapa' (chromosomes A01-A10) or 'brassica_oleracea' (C1-C9); chromosome names as in that assembly. Brassica napus is scaffold-level in Ensembl Plants (Darmor-bzh v4.1), so use B. rapa or B. oleracea for chromosome regions.

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

B3.4/5.0
Behavior3/5

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

The annotations already establish read-only, idempotent, non-destructive, open-world behavior. The description adds meaningful context beyond that: a 5 Mb region limit and the fact that results come from one Ensembl Plants genome. It still does not describe return behavior, pagination, or how the optional limit parameter affects results.

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?

The main purpose is front-loaded, and the extra sentences about species names and Brassica napus scaffolding are relevant rather than filler. The second sentence is dense but still readable, and overall the description is appropriately sized for the tool.

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?

For a read-only region query with no output schema, the description covers the core concept and important species-selection caveats. It is still incomplete for correct invocation because coordinate semantics and the optional limit parameter are not explained, and return behavior is left unspecified.

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 parameter meaning. It compensates well for species and chromosome by explaining Ensembl naming and assembly-specific chromosome names, but it leaves start/end coordinate conventions and the limit parameter unexplained.

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 states a clear verb and resource: find genes overlapping a region in one Ensembl Plants genome, with a max 5 Mb scope. It is understandable without opening the schema, but it does not explicitly differentiate this tool from nearby alternatives such as pangenome_region or expression_genes.

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?

It gives useful species-selection guidance, including the caveat that Brassica napus is scaffold-level and that B. rapa or B. oleracea should be used for chromosome regions. However, it does not explicitly say when to use this tool versus sibling tools, nor does it state when not to use it.

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