Skip to main content
Glama

bnir_expression

Read-onlyIdempotent

B. napus (ZS11) RNA-seq expression in TPM from BnIR: 'stress' (leaf and root time courses, 0.25-24 h, under salt, drought, osmotic, heat, cold 4 C and freezing -4 C, with controls at the same time points), 'hormone' (leaf and root, IAA, ACC, GA, ABA, trans-zeatin, JA, brassinolide) or 'tissue' (BnTIR: 91 libraries of bud, flower, leaf, stem, root, silique and seed stages). gene: ZS11 ID (BnaA02G0156900ZS), Darmor-bzh v4.1 name, pangenome ID, or a name/AGI (FLC, AT5G10140: all B. napus copies). Filter by treatment ('salt', 'cold') or tissue ('root'). Stress/hormone rows give each time point with the control at the same tissue and time.

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

Input Schema

NameRequiredDescriptionDefault
geneYes
tissueNo
libraryNostress
treatmentNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so the safety profile is covered. The description adds genuinely useful context the annotations do not: units are TPM, data comes from BnIR/BnTIR, and stress/hormone rows are paired with same-tissue same-time controls. It still does not disclose pagination, row counts, or error behavior for unknown gene IDs.

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 resource and data source, then progressively narrows to library modes, gene ID formats, and filters. The long parenthetical catalogs are information-dense rather than redundant, though the single-block paragraph is harder to scan than a short structured list would be.

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 no parameter descriptions in the schema, the description must carry both input and output meaning, and it does a fair job by explaining TPM units and the time-point/control row structure. Remaining gaps are modest: output shape for the 'tissue' library is unstated and no error semantics for unrecognized genes are given.

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 coverage is 0%, so the description carries the full burden and mostly succeeds: it lists accepted gene identifier formats (ZS11 BnaA02G0156900ZS, Darmor-bzh v4.1, pangenome ID, gene name/AGI with all-copy expansion) and enumerates all three 'library' values. The 'treatment' and 'tissue' filters are only illustrated with examples ('salt', 'cold', 'root') rather than enumerated, and which filters apply to which library mode is implied rather than stated.

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 a specific resource (B. napus ZS11 RNA-seq expression in TPM from BnIR) and enumerates the exact datasets covered, so an agent knows precisely what is retrieved. It stops short of naming which sibling expression tool to prefer over this one, so differentiation is left to the agent's inference.

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?

The three 'library' modes are spelled out with their contents and time-course designs, which effectively tells the agent which mode to pick for a stress, hormone, or tissue question. It also states the filter options. It gives no explicit when-not-to-use condition or named alternative among expression_genes, gene_expression, or expression_genes.

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