Skip to main content
Glama

genes_in_region

Read-onlyIdempotent

List IWGSC genes overlapping a region. chromosome like '7D'; assembly 'v2.1' (RefSeq v2.1 coordinates) or 'v1.0' (RefSeq v1.0 coordinates, v1.1 gene IDs). Region size is capped at 20 Mb.

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

Input Schema

NameRequiredDescriptionDefault
endYes
limitNo
startYes
assemblyNov2.1
chromosomeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, open-world and non-destructive behavior, and the description adds two things they don't: a hard 20 Mb region cap and the non-obvious consequence that assembly 'v1.0' returns RefSeq v1.0 coordinates with v1.1 gene IDs. These are meaningful behavioral facts an agent must know before calling.

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

Conciseness5/5

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

Two compact sentences, front-loaded with purpose followed immediately by the disambiguating parameter facts and the size cap. No filler, boilerplate, or repetition of the title.

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, so return values need not be explained, and the region cap plus assembly semantics cover the riskiest ambiguities. But with 5 parameters at 0% schema coverage, an agent still cannot tell whether start is 0- or 1-based, whether end is inclusive, or whether limit silently truncates results.

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 and it partially does: it gives a chromosome example ('7D') and disambiguates both assembly values by coordinate system and gene-ID version. However, start/end coordinate conventions and the limit parameter (default 200, truncation behavior) are left entirely undefined.

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?

Names a specific verb ('List') and resource ('IWGSC genes overlapping a region'), and the 'IWGSC genes' qualifier plus region-overlap scoping distinguishes it from gene-lookup siblings like resolve_gene or expression_genes. It stops short of explicitly contrasting with the nearest alternative, but the scope is unambiguous.

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 by the region/assembly framing; nothing states when to prefer this over expression_genes or watkins_find_genes, nor when-not to use it. The assembly choice guidance is really coordinate-system documentation rather than a use-selection rule.

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