Skip to main content
Glama

arabidopsis_function

Read-onlyIdempotent

Function of a gene through its Arabidopsis thaliana orthologue(s): Ensembl Plants Compara orthologues, then UniProtKB curated function, protein and gene names, mutant (disruption) phenotype, subcellular location and GO terms. gene: an Ensembl gene ID or name of any crop genome here, or an AGI (AT5G10140) / Arabidopsis name (FLC); in askBrassica also a B. napus pangenome gene (BnaA01g00010.1D2, BnaPanG...). one2many / many2many orthologues are all listed; the crop gene's own function is inferred, not shown.

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

Input Schema

NameRequiredDescriptionDefault
geneYes
speciesNo

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 cover safety (readOnly, idempotent, openWorld, non-destructive), so the description's real contribution is provenance and semantics: which databases are consulted, that one2many/many2many orthologues are all listed, and the important caveat that the crop gene's own function is inferred, not measured. That caveat materially affects how an agent should present results. It does not discuss failure modes for genes without Arabidopsis orthologues.

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?

Content is dense and front-loaded, with the core purpose in the first clause and input formats immediately after. The line breaks fall mid-phrase, making it slightly harder to scan than a cleanly punctuated block, but there is little wasted wording.

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 no output schema, the description correctly enumerates what is returned: curated function, protein and gene names, mutant phenotype, subcellular location, and GO terms. Combined with the orthologue-multiplicity note, an agent could call this confidently; the undocumented 'species' parameter and absent sibling guidance are the remaining gaps.

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%, so the description must carry the load; it does this well for 'gene', enumerating accepted formats (Ensembl gene ID, crop gene name, AGI code like AT5G10140, Arabidopsis name like FLC, and askBrassica pangenome IDs such as BnaA01g00010.1D2). The second parameter, 'species', is never mentioned, leaving a real gap at 0% schema coverage.

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 first clause states a specific outcome (gene function via Arabidopsis orthologues) and names the underlying resources (Ensembl Plants Compara, UniProtKB), plus the data classes returned. It does not distinguish itself from the sibling 'orthologues' tool, which is the most plausible point of confusion, so it falls short of a 5.

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 context is implied rather than stated: the reader can infer this is the tool for 'what does my crop gene do', and the note that a crop gene's own function is inferred rather than shown clarifies interpretation. However, there is no explicit when-to-use vs when-not, and no routing to siblings such as orthologues or gene_pathways.

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