Skip to main content
Glama

resistance_loci

Read-onlyIdempotent

Curated resistance loci of Brassica crops: blackleg (Leptosphaeria maculans: Rlm1-Rlm14, LepR1-3, RlmS), clubroot (Plasmodiophora brassicae: CRa, CRb, Crr1-5, Rcr1-10, PbBa...), and in Brassica vegetables downy mildew (BraDM, Pp523, BoDMR2...), Fusarium yellows (FocBo1, Foc-Br1), black rot (Xca1bo, XccBo, BRQTL...), turnip mosaic virus (retr01, retr02, ConTR01, TuRB01b, TuRB07...), Sclerotinia, soft rot and white rust QTL: source species and genotype, chromosome, pathotypes (clubroot), whether cloned, gene class and the Darmor-bzh v4.1 gene for cloned blackleg genes (Rlm2/LepR3 BnaA10g20720D; Rlm4/Rlm7/Rlm9 BnaA07g20220D), with references. query: a locus name or part ('Rlm', 'Crr', 'LepR3', 'TuRB'); disease: 'blackleg', 'clubroot', 'downy mildew', 'fusarium', 'black rot', 'TuMV', 'sclerotinia', 'soft rot', 'white rust'; chromosome: 'A07', 'C03', 'B04'.

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_loci"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNo
diseaseNo
chromosomeNo
cloned_onlyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/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. Beyond that the description adds genuinely useful content about what each record carries — source species and genotype, chromosome, pathotypes, cloned status, gene class, Darmor-bzh v4.1 gene IDs for cloned blackleg genes, and references — but says nothing about result volume, pagination, or how multiple filters combine.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Content is front-loaded: the resource and its scope come first, the enumerated diseases and returned fields follow, and the filter legend closes it out. The disease list is dense but each item earns its place by telling the agent what is searchable; only minor tightening (e.g., the '...' elisions in the gene lists) would help.

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?

There is no output schema, so the description must describe returns, and it does so concretely by listing the per-record fields and even specific Darmor-bzh gene identifiers. With zero schema coverage the only real gap is the unexplained cloned_only flag, which is the one thing an agent cannot infer from the text.

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 carries the full burden, and it mostly does: 'query' is clarified as a locus name or partial string with prefix examples ('Rlm', 'Crr'), 'disease' is effectively enumerated with valid values, and 'chromosome' is illustrated with genome-style designations ('A07', 'C03', 'B04'). The fourth parameter, cloned_only, is never mentioned, leaving one of four inputs undocumented.

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 — a curated catalogue of Brassica resistance loci — and enumerates the diseases covered (blackleg, clubroot, downy mildew, fusarium, black rot, TuMV, sclerotinia, soft rot, white rust), which is far more concrete than the bare name. The retrieval verb is only implied by the trailing 'query/disease/chromosome' filter legend, and it does not explicitly contrast itself with siblings such as resistance_gene_analogues or trait_hits.

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 conveyed by example values for each filter ('Rlm', 'Crr', 'LepR3'; 'blackleg', 'clubroot'; 'A07', 'C03', 'B04'), which implies how to search, but there is no explicit statement of when this tool is the right choice versus related tools, and no exclusions or prerequisites. An agent must infer that this is the place for named/curated loci rather than gene analogues or trait hits.

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