Skip to main content
Glama

find_gene

Read-onlyIdempotent

Look up a gene by Ensembl gene ID or gene name/symbol in Ensembl Plants: species, location, assembly, biotype, description and link. Names are searched in all of: brassica_napus, brassica_rapa (Chiifu), brassica_rapa_ro18 (R-o-18), brassica_rapa_z1 (Z1), brassica_oleracea, brassica_juncea, camelina_sativa, arabidopsis_thaliana (or only in species, if given). e.g. 'FLC', 'AT5G10140', 'BnaC09g12820D', 'Bra000001'.

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

Input Schema

NameRequiredDescriptionDefault
geneYes
speciesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, open-world, non-destructive behavior, so the bar is lower. The description still adds value by disclosing the default search breadth (all listed Brassica/Camelina/Arabidopsis species) and the shape of results (biotype, location, description, link) in the absence of an output schema.

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?

Lead sentence front-loads the core action and returns; the species enumeration is long but earns its place as a substitute for missing enum/schema documentation. Slightly dense run-on in the species clause, but 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 two-parameter read-only lookup with annotations and no output schema, the description covers input formats, default search scope, and returned fields. Only a note on matching/ambiguity behavior (e.g., multiple hits across species) is arguably missing.

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

Parameters5/5

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

With 0% schema description coverage, the description carries the full burden and does so: the gene parameter accepts both Ensembl IDs and gene symbols, backed by four concrete examples spanning Arabidopsis and Brassica formats. The species parameter's behavior (search all species vs. restrict when given) and the effective allowed species set are spelled out in the text.

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 ("Look up a gene") and scopes it to Ensembl Plants, enumerating the fields returned (species, location, assembly, biotype, description, link). It doesn't explicitly contrast with lookup-adjacent siblings such as pangenome_gene or brassica_gene_view, but the database/ID scope makes the purpose unambiguous.

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?

Conveys usage implicitly: look up one gene by ID or symbol, and the species parameter narrows the search when supplied. There is no explicit when-to-use vs when-to-use-something-else guidance or mention of alternatives for expression/pathway/orthologue lookups.

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