Skip to main content
Glama

expression_experiments

Read-onlyIdempotent

Soybean, Medicago, chickpea, pea and faba bean RNA-seq experiments held by askPulse (Expression Atlas, the Legume Information System for chickpea and pea, and faba bean studies quantified by askPulse): baseline (TPM by tissue / developmental stage / treatment) and differential (stress, pathogen, genotype contrasts). query filters descriptions/labels (e.g. 'drought', 'grain', 'Fusarium'). Gives each experiment's assay groups (baseline) or contrasts (differential).

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

Input Schema

NameRequiredDescriptionDefault
queryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint), so the remaining burden is modest. The description usefully discloses what comes back — assay groups for baseline, contrasts for differential — which no output schema provides, but says nothing about result volume, pagination, or behavior when query is omitted.

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?

Two sentences, no filler, and the species/provenance scoping is front-loaded before the capabilities. The nested parenthetical of data sources is dense and slightly hard to parse, but every clause carries information an agent needs.

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 single-optional-parameter read-only query tool with no output schema, the description covers domain scope, data sources, the two result categories, and filter semantics. The remaining gap is the return shape detail (field names, how many experiments per call), which is minor but not trivial.

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

Parameters2/5

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

Schema coverage is 0% for the single query parameter, so the description must carry the meaning and only partly does: it says query filters descriptions/labels and gives three example values. It never states the matching mode (substring vs full-text vs field-scoped) or what happens when query is null, which the schema merely sets as a default without explanation.

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?

States a specific verb+resource: RNA-seq experiments for named legumes (soybean, Medicago, chickpea, pea, faba bean), split into baseline TPM profiles and differential contrasts, with provenance (Expression Atlas, LIS, askPulse quantification). It never explicitly contrasts itself with gene-level siblings like expression_genes or gene_expression, so the boundary must be inferred from the word 'experiments'.

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 description shows the two experiment categories and explains that query filters descriptions/labels with concrete examples ('drought', 'grain', 'Fusarium'). It gives no when-not guidance, no prerequisites, and no pointer to an alternative tool for gene-level expression.

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