Skip to main content
Glama

gene_expression

Read-onlyIdempotent

Where and when a pulse and legume gene is expressed, and under which treatments it changes, from Expression Atlas, the Legume Information System for chickpea and pea, and faba bean studies quantified by askPulse. gene: Ensembl gene ID (e.g. GLYMA_01G000600, pea Psat1g000360), a chickpea CDC Frontier v3 ID (Ca1g000100) or a gene name find_gene resolves. 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

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description goes well beyond them by disclosing what is returned and how it is computed: baseline TPM medians over replicates with range, the top_groups highest-expressed tissues per experiment, and the exact differential significance cutoffs (adjusted p < 0.05, |log2FC| >= 1). It could still say more about result shape or missing-data behavior, hence not a 5.

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?

Dense but front-loaded, leading with purpose and sources before identifier formats and output semantics. Some nested parentheticals make sentences run long, but no sentence is redundant 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?

With no output schema and three undocumented parameters, the description does the necessary work by explaining both baseline and differential result semantics plus identifier formats. For a domain-specific expression lookup it is nearly complete; only edge cases (invalid gene, no significant contrasts) are unaddressed.

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 carries the full burden and largely meets it: it lists accepted gene identifier formats (Ensembl GLYMA/Psat IDs, chickpea CDC Frontier v3 Ca1g000100, or names resolvable by find_gene), explains that experiment restricts output to one accession, and that top_groups controls how many top-expressed tissues/stages are reported. The default values (10, null) and the expected format of 'experiment' are left 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 opens with a specific verb/resource statement ('Where and when a pulse and legume gene is expressed, and under which treatments it changes') and names the underlying sources (Expression Atlas, LIS, askPulse). It is clearly distinguishable from sibling tools like expression_experiments or gene_pathways, though it never explicitly contrasts itself with expression_genes.

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 reader infers this is the tool for expression profiles and that find_gene can resolve a gene name first. There is no explicit when-to-use/when-not guidance and no statement of what happens if the gene ID is ambiguous or the experiment accession is invalid.

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