Skip to main content
Glama

expression_experiments

Read-onlyIdempotent

Brassica RNA-seq experiments held by askBrassica (Expression Atlas, SRA study SRP159041 (B. napus leaf cold, heat and drought; quantified by askBrassica) and 69 B. napus SRA projects from BrassicaEDB (abiotic and biotic stress, chemical treatments, development, genotypes; experiment IDs PRJNA...)): 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.4/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds useful context about the data sources and that results are assay groups for baseline experiments or contrasts for differential experiments, but it does not discuss limits, pagination, or matching behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description front-loads the core resource but is dense and parenthetical, with substantial source-detail that could be trimmed. The key usage and return information is present, but the structure makes it harder to scan than a concise front-loaded definition would.

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 one optional parameter and no output schema, the description does a good job explaining the resource, the data sources, and the returned shape as assay groups or contrasts. It is nearly complete for this tool, with only minor gaps around result limits or pagination.

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

Parameters3/5

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

The single query parameter has 0% schema description coverage, so the description must carry the meaning. It does explain that query filters descriptions/labels and gives examples, which is helpful, but it does not clarify matching rules, multiple terms, case sensitivity, or how broad matches are ranked.

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 clearly identifies the resource as Brassica RNA-seq experiments held by askBrassica, covering baseline and differential experiments, and states that it returns assay groups or contrasts. It is specific enough to distinguish experiment-level results from gene-level expression tools, though it does not explicitly name sibling alternatives.

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 through the query filter examples such as 'drought', 'grain', and 'Fusarium', making it clear this tool finds experiments by description or label. However, there is no explicit guidance on when to use this versus expression_genes, gene_expression, or bnir_expression, and no when-not conditions are given.

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