Skip to main content
Glama

watkins_gene_trait

Read-onlyIdempotent

Compare a trait between Watkins accessions that carry vs lack a gene, per trial: n, mean and median per group and a Mann-Whitney p-value (exploratory; no correction for population structure). gene: symbol, any IWGSC RefSeq ID or pangenome gene-model ID. trait: exact name from watkins_phenotypes (e.g. 'Heading time').

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": {
      "gene": "<gene>",
      "trait": "<trait>"
    },
    "name": "watkins_gene_trait"
  }
}

Input Schema

NameRequiredDescriptionDefault
geneYes
traitYes
trialNo

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?

The annotations already cover safety: read-only, idempotent, and non-destructive. Beyond them, the description discloses the exact statistics returned (per-group n, mean, median, Mann-Whitney p-value) and an important interpretive caveat, namely no correction for population structure, which materially affects how the results should be read.

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?

It is dense but well ordered: purpose first, then returned statistics, then the caveat, then per-parameter hints. The parenthetical clauses pack in useful detail without wasted sentences, though the result is close to run-on.

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 describing the returned statistics is essential, and the description does this well. It also covers accepted gene and trait identifier formats. The gaps are the unexplained 'trial' parameter and the absence of guidance about choosing among the gene-analysis siblings.

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?

With 0% schema description coverage, the description does the heavy lifting: 'gene' accepts a symbol, any IWGSC RefSeq ID, or a pangenome gene-model ID, and 'trait' must be an exact name from watkins_phenotypes. The third parameter, 'trial', is only implied by 'per trial' and its filtering or grouping role is never explained.

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 gives a specific verb and comparison: it compares a trait between accessions that carry versus lack a gene, grouped per trial. It clearly distinguishes presence/absence grouping from haplotype-based siblings such as watkins_haplotype_trait, but it does not name those siblings explicitly.

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?

It provides a real usage constraint: it is exploratory and has no correction for population structure, and it points to watkins_phenotypes as the source of valid trait names. However, it never states when to prefer this tool over watkins_haplotype_trait or watkins_trait_genes, so the choice of approach is left to inference.

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