Skip to main content
Glama

watkins_trait_genes

Read-onlyIdempotent

Which variable genes differ in presence between Watkins accessions with high vs low values of a trait in one trial (e.g. late vs early heading). Accessions are split into top/bottom quartile (split: quartile, tercile, median) within each ancestral group (stratify_by_group) and every variable gene is tested (Cochran-Mantel-Haenszel, Benjamini-Hochberg FDR). direction 'high' = genes more frequent in high-trait accessions, 'low' the reverse. trait and trial are exact names from watkins_phenotypes(). Exploratory screen, not a GWAS.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "trait": "<trait>",
      "trial": "<trial>"
    },
    "name": "watkins_trait_genes"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
splitNoquartile
traitYes
trialYes
directionNoboth
stratify_by_groupNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/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 safety is covered; the description goes further by disclosing the statistical machinery (Cochran-Mantel-Haenszel with Benjamini-Hochberg FDR), the quartile/tercile/median splitting, per-ancestral-group stratification, and the meaning of direction high/low. It does not say anything about result size or pagination behaviour.

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 front-loaded with the core question before the methodological details, and nearly every clause carries information an agent needs. The opening sentence is long and slightly run-on, but there is no filler or repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a six-parameter exploratory statistics tool with no output schema and fully covered annotations, the description supplies the analytical model, split/stratification semantics, direction interpretation, and the source of valid trait/trial names. Only the result limit is unaddressed, which does not prevent correct invocation.

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 parameter meaning and largely does: split is explained with its three values, stratify_by_group as within-group splitting, trait/trial as exact phenotype names, and direction ('high' = more frequent in high-trait accessions, 'low' the reverse). The limit parameter and its default of 50 are never mentioned, leaving one of six parameters unexplained.

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?

The description names a specific operation on a specific resource: testing whether variable genes differ in presence between high- and low-trait Watkins accessions in one trial. It also distinguishes the scope from neighbouring work by stating 'Exploratory screen, not a GWAS', so an agent can separate it from the MTAS/GWAS-style siblings.

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?

It gives concrete prerequisites (trait and trial are exact names from watkins_phenotypes()) and a scope boundary ('Exploratory screen, not a GWAS'), which tells the agent when this is appropriate. It stops short of naming a specific alternative such as a quantitative gene-trait correlation tool, so routing is inferred rather than stated.

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