Skip to main content
Glama

trait_hits

Read-onlyIdempotent

Trait-associated positions across the genome for a chromosome overview: GWAS marker-trait associations and peaks, named trait genes and mapped trait loci held by this site, with chromosome sizes, each with a genome browser link where the assembly is loaded. trait: words to match (e.g. 'height', 'oil', 'alkaloid'); chromosome filters one chromosome. Map marker tracks are left out unless a chromosome is given. Tracks with karyotype false are on another assembly than chromosome_sizes (pulse: soybean and common bean, Ensembl chromosome numbers; faba bean on Hedin/2 v2 and projected v1; lentil CDC Redberry v2).

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

Input Schema

NameRequiredDescriptionDefault
limitNo
traitNo
chromosomeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Beyond the readOnly/idempotent/openWorld annotations, the description discloses two non-obvious behaviors: marker tracks are suppressed without a chromosome argument, and some tracks (karyotype false) live on a different assembly than chromosome_sizes, with specific examples. It does not mention pagination or the effect of limit, so it falls short of full disclosure.

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

Conciseness3/5

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

The purpose is front-loaded in the first line, but the opening sentence is a long run-on that blends purpose, outputs, and links, and the assembly caveat is a dense parenthetical with per-species detail. It is informative but not tightly structured.

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, the description does cover what comes back (positions, chromosome sizes, browser links where the assembly is loaded) plus a significant data-integrity caveat about mixed assemblies. The only real gaps are the limit parameter and whether results are truncated or paginated.

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; it explains trait as free-text matching with concrete examples ('height', 'oil', 'alkaloid') and chromosome as a single-chromosome filter that also unlocks marker tracks. The third parameter, limit, is left entirely to the schema.

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 the resource precisely (trait-associated positions, GWAS marker-trait associations and peaks, named trait genes, mapped trait loci) and states scope: genome-wide per chromosome overview, with chromosome sizes and browser links. It is clearly a trait-centric lookup, distinguishable from marker- or region-centric siblings, though the phrasing is dense and mixes purpose with caveats.

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 gives one useful conditional rule (marker tracks are omitted unless a chromosome is given) and implies querying by trait keyword, but never states when to prefer this over related tools such as legume_qtl_traits, lupin_markers, or genes_in_region. Usage is implied rather than directed.

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