Skip to main content
Glama

pangenome_accessions

Read-onlyIdempotent

Accessions in a crop pangenome with their metadata (form, genotype code, synthetic parents where known) and the number of genes each carries and lacks. dataset defaults to the first one. 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

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "pangenome_accessions"
  }
}

Input Schema

NameRequiredDescriptionDefault
datasetNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds useful non-annotation behavior: the dataset parameter defaults to the first dataset and is auto-detected from gene ID, chromosome, or accession names, and it states that returned metadata includes form, genotype code, synthetic parents and gene presence/absence counts. It says nothing about output size, pagination, or whether all accessions are returned at once, leaving a gap for a list tool.

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 is front-loaded, but the single dense paragraph buries the crucial dataset semantics inside long parentheticals listing chromosomes (chrA01-chrA10, chrC01-chrC09), gene ID formats, and accession form counts. Much of that catalog detail would be better placed in a schema enum or description, and the wall-of-text structure makes scanning harder than it needs to be.

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 simple one-optional-parameter read-only listing tool with no output schema, the description covers what is returned (metadata fields plus gene counts) and fully specifies the one parameter's valid values and defaulting behavior. Only the return cardinality/format is unaddressed, which is a minor gap given the tool's simplicity.

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

Parameters5/5

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

Schema description coverage is 0% and the schema gives no enum, so the description carries the full burden — and it does: it names the valid values ('bnapus', 'boleracea'), explains what each dataset contains, states the default (first dataset), and explains the fallback auto-detection from gene ID, chromosome, or accession name. This is meaning well beyond the bare 'dataset: string|null' schema.

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 opens with a specific resource statement: 'Accessions in a crop pangenome with their metadata ... and the number of genes each carries and lacks,' which is clearly a listing of accessions rather than genes or regions. It does not explicitly name or differentiate itself from siblings like pangenome_gene or pangenome_compare, so it falls short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to call this versus alternatives such as pangenome_gene or pangenome_compare; the reader must infer that it is the accession-level listing. The only usage-adjacent content is the defaulting rule for 'dataset' and the auto-detection note, which describe parameter behavior rather than tool selection.

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