Skip to main content
Glama

assembly_genes_in_region

Read-onlyIdempotent

Genes in a region of one of the extra Brassica assemblies (32 Brassica assemblies distributed by BnaOmics: B. napus Darmor-bzh v10, Express 617, NY7, the eight HZAU genomes (Gangan, Zheyou 73, Shengli, Tapidor, Quinta, Westar, No2127; ZS11 is the BnIR genome) and the HZAU pan-genome reference, ZS11, Westar and Laurentian ONT assemblies, ZS4-2, ZS9, HTR001, Zhongyou 821 and ZS11 (FAFU); B. carinata zd-1; B. juncea AU213 and tumida v2; B. nigra YZ12151, Ni100 v2, C2; B. oleracea HDEM, JZS v2, Korso, OX-heart; B. rapa Chiifu v3.0 and v2.5, Z1 v2 (assembly ids like Bnapus_Darmor_v10, Bnapus_Westar_ONT, Brapa_Chiifu_v3; B. napus genes are matched to Ensembl Darmor v4.1, B. rapa to Chiifu, B. oleracea to TO1000, B. juncea and B. nigra to Ensembl B. juncea, B. carinata to B. juncea + B. oleracea)) with their best Ensembl Plants match, e.g. to list candidates under a QTL or SV mapped on that assembly. assembly: assembly id; chrom as named in that assembly; at most 2 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": {
      "assembly": "<assembly>",
      "chrom": "<chrom>",
      "start": "<start>",
      "end": "<end>"
    },
    "name": "assembly_genes_in_region"
  }
}

Input Schema

NameRequiredDescriptionDefault
endYes
chromYes
startYes
assemblyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so safety behavior is covered. The description adds useful constraints such as 'at most 2 Mb' and explains that results include the best Ensembl Plants match, but it omits coordinate conventions, invalid-input behavior, and return details.

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

Conciseness2/5

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

The first sentence is extremely long and dominated by a parenthetical catalog of assemblies, which buries the core purpose and parameter constraints. The details are relevant but poorly front-loaded and would be better placed in schema or separate documentation.

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 4-parameter region query with no output schema, the description covers the assembly landscape and a representative use case. However, it is incomplete on coordinate semantics and does not describe the return structure beyond saying genes come with their best Ensembl Plants match.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/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 burden. It clarifies assembly IDs and that chrom must be named as in that assembly, but it leaves start and end unexplained beyond the overall 2 Mb span limit, including no mention of coordinate system or inclusivity.

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 specific verb and resource: genes in a region of an extra Brassica assembly, with their best Ensembl Plants match. It is clear what the tool does and implies assembly-specific scope, though it does not explicitly contrast with sibling tools such as genes_in_region.

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?

The description gives a concrete use case: listing candidates under a QTL or SV mapped on that assembly. It does not provide explicit exclusions or name alternatives, but the context for when to use this tool is clear.

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