Skip to main content
Glama

pangenome_gene

Read-onlyIdempotent

Presence/absence of a gene across the accessions of a crop pangenome: how many accessions carry it, core or variable, which accessions lack it (and which carry it, if fewer), location, description and genome browser link. gene: a pangenome gene ID, a B. napus Ensembl (Darmor-bzh v4.1: GSBRNA2T..., BnaA01g00010D) or BnIR ZS11 gene ID (mapped to the pangenome gene), or words from the protein description (e.g. 'flowering locus C') to list matching genes. B. napus genes come with their Ensembl v4.1 and ZS11 counterparts. 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": {
      "gene": "<gene>"
    },
    "name": "pangenome_gene"
  }
}

Input Schema

NameRequiredDescriptionDefault
geneYes
limitNo
datasetNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover the safe-read profile, and the description goes further by disclosing what comes back (presence/absence lists, core/variable classification, browser link) and the automatic dataset-detection behavior. It stops short of stating response size limits or pagination for large match sets.

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 core purpose is front-loaded in the first sentence, but the rest is one dense undifferentiated block mixing ID syntax, dataset inventories and accession taxonomy without line breaks or ordering. The accession 'form' breakdown is background reference rather than something needed to call the tool.

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?

For a read-only lookup with no output schema, the definition supplies enough to call it correctly: accepted identifiers, dataset selection and inference, and an outline of the return content. Missing pieces are the meaning/effect of 'limit' and how multi-gene matches from free-text queries are ordered or capped.

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

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage the description must carry the parameters, and it does so thoroughly for 'gene' (three accepted ID/name forms with examples) and 'dataset' (two enumerated values with full composition and chromosome naming). The 'limit' parameter is never explained, which is the only real gap.

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 states a specific verb and resource: presence/absence of a gene across accessions of a crop pangenome, then enumerates the returned facts (carrier count, core vs variable, which accessions lack it, location, description, browser link). An agent can distinguish this from region- or gene-lookup siblings without opening the schema.

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 tells the agent which inputs are accepted (pangenome gene IDs, B. napus Ensembl/Zs11 IDs, free-text protein-description words) and explains that the dataset is inferred from the ID, chromosome or accession names, so the agent knows when it can omit 'dataset'. It does not explicitly say when to prefer a sibling tool instead, which keeps it from a 5.

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