Skip to main content
Glama

pulse_gene_view

Read-onlyIdempotent

Interactive gene view for one pulse and legume gene: a relationship map of its orthologues across legumes (Ensembl Compara), members of its LIS legume gene family (chickpea, lentil, pea, soybean, Medicago), Arabidopsis function, expression contrasts and recent papers, with tabs for the gene family by species and baseline expression (LIS chickpea and pea atlases, Expression Atlas). 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": "pulse_gene_view"
  }
}

Input Schema

NameRequiredDescriptionDefault
geneYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds genuinely non-structured behavior: it is an interactive UI rendered in chat for MCP Apps clients, and for other clients the result still returns nodes, panel data and a shareable gene page link. That dual-mode disclosure is exactly the kind of context annotations cannot express. Minor gap: no indication of latency or size of the underlying aggregation.

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?

The most important information (what the view is, for which gene) is front-loaded, and the subsequent clauses are dense but each carries content about what the view contains or returns. It reads as one long run-on enumeration, which is slightly heavy, but nothing is padding.

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 fairly complex aggregation tool with no output schema and a single undocumented parameter, the description does the necessary work: it explains the rendered content, the fallback return payload, and the gene identifier format. What is missing is any notion of data freshness, partial-failure behavior across the many upstream sources, or response size, which matters for a tool that fans out to Compara, Expression Atlas and literature.

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 description coverage is 0% for the single required parameter, so the description must carry the load, and it does partially by closing with 'gene: gene name or Ensembl/LIS ID.' That names the accepted identifier formats, which the schema does not. It does not clarify ambiguity handling (e.g., what happens if a symbol maps to multiple genes) or whether it accepts IDs from Ensembl Plants versus LIS only.

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 gives a concrete verb+resource ('Interactive gene view for one pulse and legume gene') and then enumerates exactly what the view aggregates: orthologues across legumes, LIS family members by species, Arabidopsis function, expression contrasts, recent papers. That enumeration lets an agent infer this is an all-in-one composite view rather than a single-purpose lookup. It stops short of naming the sibling tools it subsumes (orthologues, gene_expression, get_paper), so the differentiation is implicit rather than stated.

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 by the phrase 'one pulse and legume gene', which scopes the tool to legume genes and signals a broad overview use case, but there is no explicit when-to-use/when-not language and no routing to alternatives such as orthologues or gene_expression for narrower questions. An agent can infer the use case but must reason about it.

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