Skip to main content
Glama

pangenome_compare

Read-onlyIdempotent

Genes whose presence frequency differs most between two groups of pangenome accessions (accession names from pangenome_accessions, 'form:' selectors such as 'form:Synthetic' or 'form:cauliflower', or ['all']). min_diff is the minimum absolute frequency difference (0-1); positive diff = more frequent in group_a. 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": {
      "group_a": "<group_a>",
      "group_b": "<group_b>"
    },
    "name": "pangenome_compare"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
datasetNo
group_aYes
group_bYes
min_diffNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare this read-only, idempotent and open-world, so the description just needs added context, and it supplies plenty: dataset auto-detection from gene IDs, chromosomes or accessions, the two specific pangenome builds with gene ID formats, and the meaning of positive vs negative diff. It does not describe result ordering, truncation, or what happens when a group is very large.

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?

Information density is high and the purpose is front-loaded, but the body is one undifferentiated run-on block mixing parameter rules, dataset catalogs, and botanical reference detail (parentage, accession counts per form). Splitting into usage / parameters / datasets sections would improve scannability without losing content.

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 five-parameter analysis tool with no output schema, the description covers the hard parts: dataset ambiguity, ID naming, group specification, and threshold semantics. It remains incomplete on limit behavior and on the shape of the result (ranked gene list? diff values?), which an agent would need to interpret the response.

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?

Schema coverage is 0%, so the description carries the full burden, and it defines group_a/group_b (accession names, form selectors, ['all']), min_diff (absolute 0-1 difference, signed interpretation), and dataset (with values and contents). The one gap is 'limit', which the schema defaults to 100 but the description never mentions or explains.

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 first sentence states a specific operation (find genes whose presence frequency differs most between two groups) on a named resource (pangenome accessions), with the direction convention spelled out. It partially distinguishes itself from siblings by pointing to pangenome_accessions as the source of accession names, though it never explicitly says how it differs from related lookup tools like pangenome_gene.

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 gives concrete conditions for inputs: accession names come from pangenome_accessions, 'form:<form>' selectors are accepted, and ['all'] is a valid group. It also explains the min_diff threshold semantics. It stops short of saying when not to use it or naming an alternative comparison tool.

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