Skip to main content
Glama

resistance_gene_analogues

Read-onlyIdempotent

Resistance gene analogues (RGAs) in the B. napus pangenome (1,749 genes: NBS-LRR classes TNL, CNL, RNL, NL, TN, CN, RN, NBS, TX; receptor-like kinases RLK; receptor-like proteins RLP), with presence/absence across the 53 pangenome accessions, description and location (Darmor-bzh v8.1 with pangenome contigs). Filter by chromosome ('A10'; with start/end in bp for a region), a pangenome gene ID, rga_class ('NLR' for all NBS-LRR classes, or 'TNL', 'RLK', 'RLP'...) and variable_only (genes absent from some accessions).

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

Input Schema

NameRequiredDescriptionDefault
endNo
geneNo
limitNo
startNo
rga_classNo
chromosomeNo
variable_onlyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds real domain context beyond that: the dataset size, the class taxonomy, that presence/absence is reported across 53 accessions, and the coordinate reference genome — all useful for interpreting results. It does not mention pagination or the default limit behaviour.

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?

Content is front-loaded and every clause carries information, but it is delivered as one dense parenthetical-heavy sentence that is harder to parse than a short structured list of filters would 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 7-parameter, no-output-schema query tool, the description covers the domain, the coordinate system, and the semantics of the non-obvious filters. The remaining gap is the result-set cap (limit default 200) and any indication of what fields each record returns, though 'description and location' is named.

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 description coverage is 0%, so the description must carry the load, and it largely does: chromosome with start/end in bp for a region, a pangenome gene ID, rga_class with the important clarification that 'NLR' returns all NBS-LRR classes while 'TNL'/'RLK'/'RLP' return specific ones, and variable_only meaning genes absent from some accessions. Only 'limit' (default 200) is left unexplained.

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 names a specific resource (RGAs in the B. napus pangenome) and enumerates its scope: 1,749 genes, the NBS-LRR subclasses, RLK/RLP families, presence/absence across 53 accessions, and location on Darmor-bzh v8.1. That is far more specific than the name alone, though it never explicitly contrasts itself with neighbours like resistance_loci or 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 Guidelines3/5

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

Usage is only implied through the filtering options (chromosome region, gene ID, rga_class, variable_only) — the agent can infer this is a filtered lookup of RGA records. There is no explicit statement of when to prefer it over resistance_loci, genes_in_region, or find_gene, and no exclusions.

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