Skip to main content
Glama

pangenome_region

Read-onlyIdempotent

Pangenome genes in a region (max 5 Mb) with how many accessions carry each, e.g. to see which genes in a QTL interval show presence/absence variation. chromosome like 'A01' or 'chrA01'. Datasets: 'bnapus' = B. napus pangenome (Darmor-bzh v8.1 plus 52 accessions, 94,013 genes; IDs like BnaA01g00010.1D2 for Darmor v8.1 genes and BnaPanG000163 for novel pangenome genes; chromosomes chrA01-chrA10, chrC01-chrC09); 'boleracea' = B. oleracea pangenome (TO1000 reference plus broccoli, Brussels sprouts, cabbage x2, cauliflower x2, kale, kohlrabi and B. macrocarpa; IDs Bo1g001000.1 = Ensembl Plants B. oleracea gene Bo1g001000, novel genes BOLEPAN_00000379.1; chromosomes C1-C9 of the BOL assembly). The dataset is detected from the gene ID, chromosome or accession names when not given. Accessions have a 'form': bnapus Oilseed (24), Synthetic (20, resynthesized from B. rapa x B. oleracea, with parents), Fodder (3), Vegetable (2), Swede (2), Elite (2); boleracea broccoli, cauliflower, cabbage, Brussels sprouts, kale, kohlrabi, reference line, wild relative.

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": "pangenome_region"
  }
}

Input Schema

NameRequiredDescriptionDefault
endYes
limitNo
startYes
datasetNo
chromosomeYes
variable_onlyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/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 is covered. The description adds genuinely new behavioral facts: a hard 5 Mb region cap and automatic dataset detection from gene ID, chromosome or accession names when the dataset argument is omitted. It omits what happens when results exceed the default limit of 300 (truncation vs pagination), which is the main remaining behavioral gap.

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 purpose and constraints are front-loaded in the first two sentences, which is good structure. The remainder is a dense wall of dataset metadata, and detail such as accession form counts (Oilseed 24, Synthetic 20, Fodder 3, Swede 2) and parent-cross descriptions does not change how the tool is invoked — it is trivia padding out a parameter choice.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/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 correctly signals the return content (genes plus per-gene accession counts), and it covers the region-size limit and dataset ambiguity. An agent still lacks coordinate semantics for start/end and any statement on result truncation at the limit default, which matters for a 5 Mb region.

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% across six parameters, so the description must carry the load. It does well on two of them — chromosome naming ('A01' or 'chrA01') and the two legal dataset values with their reference assemblies, chromosome sets and ID formats, plus detection fallback behavior. It says nothing about start/end coordinate convention, the limit parameter, or what variable_only filters, leaving four parameters undocumented.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening clause gives a specific verb+resource+payload: pangenome genes in a region plus how many accessions carry each. The 'pangenome' qualifier and the accession-count payload are exactly what separates it from the reference-genome sibling genes_in_region, and the QTL presence/absence example anchors the intent.

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?

It supplies a concrete when-to-use scenario ('to see which genes in a QTL interval show presence/absence variation') and an implicit scope limit of 5 Mb. It does not name a preferred alternative (e.g. genes_in_region for single-reference lookups, pangenome_gene for a single gene) or state when not to use it, so it stops short of full routing guidance.

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