Skip to main content
Glama

brassica_gene_view

Read-onlyIdempotent

Interactive gene view for one Brassica gene: a relationship map of its orthologues in B. rapa, B. oleracea, B. juncea, Camelina and Arabidopsis, Arabidopsis function, presence/absence across the B. napus (53 accessions) or B. oleracea (10) pangenome by crop form, BnIR stress responses (ZS11 copies), Expression Atlas contrasts and recent papers, with tabs for pangenome presence by form, a BnIR stress time-course heatmap and baseline expression. Clients that support MCP Apps show it in the chat; the result also lists the nodes, the panel data and the gene page link (page) to share. gene: gene name or Ensembl/LIS ID.

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

Input Schema

NameRequiredDescriptionDefault
geneYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, open-world and non-destructive, so the safety profile is covered. The description usefully adds that rendering is client-dependent and that the call also returns nodes, panel data and a shareable gene page link, which is real behavior beyond the annotations, but it says nothing about cost, latency, or failure modes for invalid identifiers.

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

Conciseness2/5

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

One very long run-on sentence chains a dozen data domains together with commas, then tacks the 'gene:' spec fragment onto the end with no formatting. Every clause carries information, but the lack of structure makes it hard to scan and the parameter note is buried in a trailing fragment.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a composite visualization tool with no output schema, describing returned content (relationship map, nodes, panel data, page link) is the right move and is largely done. However, nothing explains what happens with MCP clients that lack Apps support, whether the same data is reachable individually via siblings, or how to interpret the tab structure programmatically.

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?

Schema coverage is 0% and the only parameter is an untyped 'Gene' string, so the description's 'gene name or Ensembl/LIS ID' genuinely adds accepted identifier formats beyond the schema. That is a meaningful addition but stops short of example values or whether IDs for the non-Brassica species (e.g. Arabidopsis AGI codes) are accepted.

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 (an interactive view of one Brassica gene) and enumerates exactly what the view aggregates: orthologue relationships, Arabidopsis function, pangenome presence, BnIR stress data, expression contrasts and papers. It is clear what the tool produces, but it never contrasts itself with the composite siblings that cover subsets (orthologues, gene_expression, pangenome_gene, arabidopsis_function), so an agent must infer the difference.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use guidance and no mention of alternatives, despite many sibling tools exposing overlapping data. The only contextual hint is that MCP-Apps-capable clients render it in chat, which is about presentation, not tool selection.

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