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).

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.6/5.0
Behavior3/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 adds genuine behavior context beyond that: browser links only appear where the assembly is loaded, and tracks with karyotype false sit on a different assembly than chromosome_sizes (soybean, common bean, Ensembl numbering). That cross-assembly caveat is useful but the final sentence is cryptic and under-explained rather than actionable.

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 returned content is front-loaded, which is right, but the text runs as one dense, clause-chained sentence set with parenthetical asides ('pulse: soybean and common bean, Ensembl chromosome numbers') that read like internal notes. Information density is high, yet readability suffers and no structure separates return content from parameter semantics from caveats.

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 the work of describing what comes back (positions, peaks, trait genes, chromosome sizes, browser links), and annotations cover the safety profile. Remaining gap is the undocumented limit parameter and the vague treatment of the assembly/karyotype caveat, but an agent could call this correctly from what is given.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the burden. It clarifies two of three parameters well: 'trait: words to match' with concrete examples ('height', 'oil', 'alkaloid'), and 'chromosome filters one chromosome'. The limit parameter (default 300) is never mentioned in either the schema or the description, leaving its behavior undocumented.

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 precisely what corpus is returned: GWAS marker-trait associations and peaks, named trait genes, mapped trait loci, chromosome sizes, and browser links for a chromosome overview. It is specific about scope (trait-associated positions) rather than restating the name. It stops short of naming which sibling covers adjacent needs (e.g. bnir_gwas or genes_in_region), so differentiation is inferential.

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?

'Map marker tracks are left out unless a chromosome is given' is an explicit conditional telling the agent when to supply a filter to get complete results, and 'chromosome filters one chromosome' bounds the query. What is missing is routing guidance: no statement of when to prefer this over sibling GWAS or region 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