Skip to main content
Glama

legume_genes_in_region

Read-onlyIdempotent

Chickpea, lentil or extra faba bean genes in a region (max 5 Mb) with descriptions, gene families, curated lentil gene lists and best matches. dataset 'chickpea' (CDC Frontier v3, chromosomes chr1-chr8), 'chickpea_kabuli_v1' (UWA kabuli v2.6.3, Ca1-Ca8), 'chickpea_desi' (UWA desi v3.0, Ca1-Ca8), 'lentil' (CDC Redberry v2, Chr1-Chr7), 'lentil_greenstar' (Lcu.1GRN.Chr1-7), 'lentil_ervoides' (Ler.1DRT.Chr1-7), 'faba_v2' (Hedin/2 v2, chr1_partA, chr1_partB, chr2-chr6) or 'faba_tiffany' (chr1S, chr1L, chr2-chr6). Chromosome numbers alone (e.g. '4') are accepted for chickpea and lentil.

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": {
      "dataset": "<dataset>",
      "chromosome": "<chromosome>",
      "start": "<start>",
      "end": "<end>"
    },
    "name": "legume_genes_in_region"
  }
}

Input Schema

NameRequiredDescriptionDefault
endYes
limitNo
startYes
datasetYes
chromosomeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/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 bar is lower; the description still adds real behavior beyond them by stating the 5 Mb region cap, the returned payload contents, and the per-dataset coordinate systems. It stops short of describing pagination or truncation behavior for the limit parameter.

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 is front-loaded in the first clause, and the long dataset enumeration is justified because the schema has no enums. The prose is dense but nearly every clause carries information an agent needs to form a valid call.

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?

There is no output schema, and the description only sketches the return payload rather than explaining its shape. Combined with unspecified coordinate units and limit semantics on a 5-parameter query tool, the definition is workable but leaves gaps an agent must guess at.

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 carries the burden. It does this well for the two hardest parameters, listing all eight valid dataset keys with their assembly and chromosome naming schemes and confirming that bare chromosome numbers are accepted. However, start, end and limit receive no explanation of units (bp), coordinate basis, or what limit=300 truncates.

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 (genes in a region) and enumerates what comes back: descriptions, gene families, curated lentil gene lists and best matches. It also scopes the resource to chickpea, lentil and faba. It does not explicitly distinguish itself from the sibling genes_in_region, 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?

The 5 Mb maximum region size and the chromosome-naming conventions imply when the tool is callable, but there is no explicit statement of when to pick this over genes_in_region, gene_neighbourhood, or find_gene. Usage is inferable rather than stated.

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