Skip to main content
Glama

resolve_gene

Read-onlyIdempotent

Resolve a wheat gene symbol (e.g. Lr34, Rht-B1) or IWGSC gene ID in any RefSeq version (v1.0 TraesCS..01G, v1.1 TraesCS..02G, v2.1 TraesCS..03G, CSS2014 Traes_..) to all versions, genomic locations, curated symbol/trait (with verification status), Watkins pangenome presence and links.

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": {
      "identifier": "<identifier>"
    },
    "name": "resolve_gene"
  }
}

Input Schema

NameRequiredDescriptionDefault
identifierYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld, so the safety profile is covered; the description adds real value by enumerating the return payload (all version mappings, genomic locations, curated symbol/trait with verification status, pangenome presence, links). It stops short of noting behavior on unresolvable identifiers or ambiguous symbols.

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

Conciseness5/5

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

One front-loaded sentence with the verb first; the parenthetical examples and version list each earn their place by specifying valid input formats. No filler.

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 usefully enumerates what is returned, and the single-parameter scope is well matched. Minor gap: no statement on behavior for unknown or ambiguous identifiers.

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

Parameters4/5

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

Schema coverage is 0%, so the description must carry the single identifier parameter; it does so by illustrating valid symbol forms and the four ID version conventions, which meaningfully constrains what to pass. It does not address ambiguity handling when a symbol maps to multiple genes.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Specific verb 'Resolve' paired with a concrete resource (wheat gene symbol or IWGSC gene ID), and it names real examples (Lr34, Rht-B1) plus the exact accession formats across RefSeq versions, so the agent knows precisely what input shape lands here.

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?

The accepted identifier types imply when the tool applies, but there is no explicit statement of when to use it versus siblings like gene_expression or wheat_gene_view, and no stated exclusions or failure conditions.

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