Skip to main content
Glama

expression_experiments

Read-onlyIdempotent

Bread wheat RNA-seq experiments held by askWheat (Expression Atlas and SRA study SRP045409 (seedling drought, heat and combined stress; quantified by askWheat)): 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

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered. The description contributes the data provenance and the shape of results (assay groups vs. contrasts), but says nothing about result volume, pagination, or whether the query is a substring match vs. token match, which matters for an open-world search.

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?

Information is front-loaded with the resource and provenance, followed by filtering behavior and return shape. The nested parenthetical about SRA study details is dense but earns its place as provenance. No filler sentences.

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 tool with annotations and no output schema, the description covers what the tool serves, how to filter, and what each result contains. Only minor gaps remain (default behavior with no query, matching semantics).

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% and the single optional 'query' parameter is undocumented in the schema, so the description carries the full burden. It does so reasonably: it states that query filters descriptions/labels and gives three concrete example values, which lets an agent construct a valid call. It omits the null/omit-returns-everything behavior.

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 (bread wheat RNA-seq experiments in askWheat), its upstream sources (Expression Atlas, SRA SRP045409), and the two result modes (baseline assay groups vs. differential contrasts). It is clear what the tool returns, though it does not explicitly contrast itself with siblings like expression_genes or gene_expression.

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 only implied through the query examples ('drought', 'grain', 'Fusarium'), which suggest keyword filtering of experiment descriptions. There is no explicit statement of when to pick this tool over gene-level expression tools, nor any guidance on omitting the query to list all experiments.

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