Skip to main content
Glama

legume_pangene

Read-onlyIdempotent

The same gene across chickpea or pea assemblies and annotation versions, from LIS pangene sets (synteny-aware clustering). Chickpea (Cicer.pan3): kabuli CDC Frontier v3 (Ca1g000200), v1/v2 (Ca_00003), desi ICC 4958 (Ca_) and wild C. reticulatum (Cr1g…) and C. echinospermum (Ce…). Pea (Pisum.pan1): Cameor v1a (Psat1g000360 = Ensembl pisum_sativum), Cameor v2 (Psat.1g…), JI2822 (PSAT_LOCUS… = Ensembl JI2822) and ZW6 (Psat01G…). gene: any of these IDs or a pangene ID. Use it to convert IDs between assemblies (e.g. a kabuli Ca_ ID from a paper to the v3 gene with expression data). dataset ('chickpea_desi', 'chickpea_kabuli_v1', ...) disambiguates a shared Ca_ 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": "legume_pangene"
  }
}

Input Schema

NameRequiredDescriptionDefault
geneYes
datasetNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, open-world), so the description's job is to add domain behavior—and it does: it explains that results come from synteny-aware pangene clustering and that identical-looking Ca_ IDs can be ambiguous unless dataset is supplied. It stops short of saying what a lookup returns when a gene has no pangene assignment or how multiple hits are handled.

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?

Purpose and the key conversion use case are front-loaded, with the ID-format and dataset details following as supporting reference. The assembly/ID listing is dense and bulky, but given 0% schema coverage that detail is doing real work rather than padding.

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 two-parameter lookup with no output schema, the description thoroughly covers inputs and intent but says nothing about the return shape—whether the agent gets one pangene group, all member IDs across assemblies, or a miss indicator. That is the main remaining gap an agent would want filled before calling.

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 parameters, and it largely does: gene accepts the enumerated ID formats per dataset or a pangene ID, and dataset is described as the disambiguator with example values. The dataset value list is illustrative ('chickpea_desi', 'chickpea_kabuli_v1', ...) rather than complete, leaving some guesswork about valid strings.

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 concrete resource (the same gene across chickpea/pea assemblies and annotation versions) and a concrete operation (converting IDs between assemblies via LIS pangene sets). It is clear what the tool resolves, though it never explicitly distinguishes itself from siblings like legume_gene or find_gene, so the agent must infer the boundary.

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

Usage Guidelines4/5

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

It gives a clear usage scenario: 'Use it to convert IDs between assemblies (e.g. a kabuli Ca_ ID from a paper to the v3 gene with expression data)', plus a hint that dataset disambiguates shared IDs. There is no explicit when-not-to-use or named alternative, which keeps it short of a 5.

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