Skip to main content
Glama

gene_expression

Read-onlyIdempotent

Where and when a wheat gene is expressed, and under which treatments it changes, from Expression Atlas and SRA study SRP045409 (seedling drought, heat and combined stress; quantified by askWheat). gene: symbol or any IWGSC RefSeq ID (converted to v1.1, as used by Atlas). Baseline: TPM (median over replicates, with range) for the top_groups highest-expressed tissues/stages per experiment. Differential: every contrast where the gene is significant (adjusted p < 0.05, |log2FC| >= 1). 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": "gene_expression"
  }
}

Input Schema

NameRequiredDescriptionDefault
geneYes
experimentNo
top_groupsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, open-world behavior, but the description adds real substance: baseline TPM as median over replicates with range, top-N highest-expressed tissues/stages, and the exact differential significance thresholds (adj p < 0.05, |log2FC| >= 1). It also discloses an implicit transformation (IDs converted to v1.1). It does not say what happens when a gene has no significant contrasts or when an ID fails conversion.

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?

Front-loaded with the purpose and data source, then parameter semantics in a compact sequence; every clause carries information about inputs or returned content. The parenthetical density (replicate statistics, thresholds, ID-version caveat) makes it dense but not padded.

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 3-parameter tool with no output schema, the description does the necessary work of explaining what comes back (median TPM with range for top groups, significant contrasts) and how calls are scoped. It falls short only on the accession format for experiment and on the shape of results when no differential contrasts pass the thresholds.

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 coverage the description carries the full burden, and it defines all three parameters: gene accepts a symbol or any IWGSC RefSeq ID with v1.1 conversion, top_groups caps the highest-expressed tissues/stages per experiment, and experiment restricts to a single accession. The gap is that no example or format for an experiment accession is given, so the agent must guess valid values.

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 specific verb and resource ('Where and when a wheat gene is expressed, and under which treatments it changes') plus concrete data provenance (Expression Atlas, SRA study SRP045409, askWheat quantification). It clearly distinguishes itself from sibling expression tools by returning both baseline and differential expression for one gene, rather than experiments or gene lists.

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 is implied rather than stated: the note that 'experiment restricts to one accession' hints that a separate tool lists experiments, and the drought/heat stress framing tells the agent what data it covers. There is no explicit when-to-use/when-not phrasing or named alternative (e.g. expression_experiments to discover accessions), so the agent must infer routing.

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