Skip to main content
Glama

ozwheat_mtas

Read-onlyIdempotent

Marker-trait associations from the OzWheat GWAS (285 Australian and international wheat cultivars and lines; glasshouse 2016 and field trials at Canberra 2018-19, Wagga 2018, Narrabri 2019). Traits: days to anthesis, days to heading, degree-days to heading ('flowering'/'heading') and plant height. Filter by trait, gene (symbol or any IWGSC ID; matches the gene carrying the SNP or the linked candidate gene, or the name in their annotation) and/or region (chromosome like '7B' with start/end in RefSeq v1.0 bp). Each MTA gives the peak SNP and its position, p-value, the gene it sits in (with v1.1/v2.1 IDs), any literature candidate gene, and the allele effect: trait mean (BLUE) of lines carrying each allele in that trial.

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

Input Schema

NameRequiredDescriptionDefault
endNo
geneNo
limitNo
startNo
traitNo
chromosomeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful behavior beyond that: exact result contents (peak SNP and position, p-value, gene with v1.1/v2.1 IDs, literature candidate gene, per-allele BLUE trait means) and the non-obvious gene-matching semantics. It does not mention pagination or the 50-row default cap, which is a real gap for a list-returning tool.

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?

The definition is dense but front-loaded: dataset and provenance first, then traits, then filter semantics, then return shape. Every sentence carries information, but the parenthetical trial lists and chromosome-ID asides make single sentences long and harder to scan than necessary.

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 six-parameter, no-output-schema tool with zero schema coverage, the description supplies the domain vocabulary, coordinate reference, matching rules and return fields an agent needs. Missing pieces are the default limit/truncation behavior and whether an unfiltered call returns the full association set or a capped slice.

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 compensate, and it does for most parameters: 'trait' vocabulary is enumerated, 'gene' accepts a symbol or any IWGSC ID with three matching modes spelled out, and 'chromosome'/'start'/'end' are defined with an example ('7B') and the RefSeq v1.0 bp coordinate system. The 'limit' parameter is never explained, and it is not stated that start/end are meaningless without a chromosome.

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 states a concrete resource (marker-trait associations from the OzWheat GWAS) and enumerates its scope: 285 cultivars/lines, specific trials, and four trait categories. An agent can tell what data comes back. It never contrasts itself with plausible siblings such as trait_hits or snp_markers, so it stops 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 Guidelines3/5

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

Usage is implied rather than stated: the filter set (trait, gene, region) signals when this tool is appropriate, and 'and/or' hints the filters compose. There is no explicit when-to-use/when-not guidance, no prerequisite notes, and no named alternative for the overlapping trait-hit and marker tools.

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