Skip to main content
Glama

wheat_homoeologue_expression

Read-onlyIdempotent

Relative expression of a wheat gene's A, B and D homoeologues per tissue/stage (Expression Atlas baseline experiments), with the homoeologue expression balance category of each tissue: balanced, A/B/D dominant or A/B/D suppressed, by distance to the ideal proportions (Ramirez-Gonzalez et al. 2018). Categories are given only for 1:1:1 triads with summed TPM >= 0.5. experiment restricts to one accession.

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>"
    },
    "name": "wheat_homoeologue_expression"
  }
}

Input Schema

NameRequiredDescriptionDefault
geneYes
experimentNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description adds real substance beyond them: the classification thresholds (only 1:1:1 triads with summed TPM >= 0.5), the category scheme, the distance-to-ideal methodology and its citation. It stops short of describing return shape or pagination, but that is a minor gap given the annotation coverage.

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?

Four dense sentences that front-load the output and then qualify it with the classification rules; no wasted words. The line wrapping and mid-sentence clause joining slightly hurt scanability but nothing is filler.

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 2-parameter, no-output-schema tool, the description explains what is measured, how categories are derived and their eligibility rules, and the effect of the optional parameter. Missing only the 'gene' identifier format and whether omitting 'experiment' aggregates across experiments, which an agent would need to call correctly.

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, and it only partially does: it explains that 'experiment' restricts to one accession — useful behavior not in the schema — but says nothing about the required 'gene' parameter's accepted format (gene ID? symbol? identifier namespace?).

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?

States a precise verb+resource: relative expression of a wheat gene's A/B/D homoeologues per tissue/stage, plus the homoeologue-balance category assigned to each tissue. The narrow homoeologue-triads framing distinguishes it clearly from generic siblings like gene_expression or expression_genes without needing to name them.

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 context is implied by the data source (Expression Atlas baseline experiments) and by the topic (homoeologue balance in 1:1:1 triads), and it notes that 'experiment restricts to one accession.' However, it never says when to pick this over sibling expression tools, nor what happens when no experiment is supplied (all experiments aggregated?).

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