Skip to main content
Glama

bnir_gwas

Read-onlyIdempotent

Genome-wide association peaks for B. napus traits from BnIR (HZAU): 135 traits from 10 GWAS studies (seed oil fatty acids and erucic acid, glucosinolates, oil content, flowering time, plant height, branching, silique and seed traits, cadmium, salt and other stress responses...). Each peak (adjacent 500-kb windows with p <= 1e-6) gives the study, lead SNP with alleles, consequence, p-value, effect (beta) and variance explained, and the genes within 25 kb of the lead SNP with their Arabidopsis best hit and Darmor-bzh v4.1 ID (= Ensembl Plants B. napus). Search by trait words ('erucic', 'flowering'), a ZS11 region (chromosome 'A08' with start/end in bp), or gene (ZS11 BnaA08G0133900ZS, Darmor v4.1 BnaA08g11040D, Arabidopsis AGI or name such as FAE1). No arguments lists the traits.

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

Input Schema

NameRequiredDescriptionDefault
endNo
geneNo
limitNo
max_pNo
startNo
traitNo
chromosomeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/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 the peak-calling methodology and gene-proximity window (25 kb), which is real added context. It does not discuss result caps, ranking, or what happens when multiple studies report the same trait.

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?

Front-loaded with what the tool returns, then the peak criteria, then the search modes and the no-argument behavior - a sensible order. The parenthetical trait inventory is somewhat long but helps an agent pick trait keywords, so it largely earns its space.

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?

With no output schema and zero schema description coverage across 7 parameters, the description compensates well by listing returned fields (study, lead SNP with alleles, consequence, p-value, beta, variance explained, nearby genes with Arabidopsis best hit and Darmor-bzh ID). The main omissions are the limit parameter's behavior and result ordering/pagination.

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 must carry the load, and it does for most parameters: trait accepts words like 'erucic' or 'flowering', chromosome/start/end define a ZS11 region in bp, and gene accepts ZS11, Darmor v4.1, Arabidopsis AGI or a name such as FAE1. It implies the p-value threshold behind max_p but never mentions the limit parameter or its default of 30.

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?

States a specific resource (GWAS peaks for B. napus traits from BnIR/HZAU) with concrete scope: 135 traits, 10 studies, named trait classes. The peak definition (adjacent 500-kb windows with p <= 1e-6) makes it unmistakably distinct from siblings like bnir_expression 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 Guidelines4/5

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

Explicitly enumerates the three query modes - trait words, ZS11 region (chromosome plus start/end in bp), or gene ID - and notes that no arguments lists the traits, which is a genuinely useful entry point. It stops short of naming when to prefer a sibling such as genes_in_region or trait_hits over this 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