Skip to main content
Glama

legume_qtl_traits

Read-onlyIdempotent

Traits with QTL or GWAS results, with counts per species (soybean (SoyBase QTL on genetic maps plus GWAS; marker positions on Wm82.a2 = Ensembl glycine_max), common bean (G19833 v1 = Ensembl phaseolus_vulgaris; some GWAS on G19833 v2), cowpea (IT97K-499-35 v1) and peanut (Tifrunner v2) from LIS; faba bean QTL markers from 56 studies (Faba Bean Genome Consortium compilation, positions on Hedin/2 v2 and projected to the Ensembl Hedin/2 v1 assembly); lentil protein and amino acid GWAS on the diversity panel (KnowPulse, CDC Redberry v2 = LIS lentil genes); chickpea, lentil, pea, faba bean, lupin, grass pea and pigeonpea QTL and GWAS from pulsedb.org (Cool Season Food Legume Database)). query filters trait names (e.g. 'seed', 'rust').

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "legume_qtl_traits"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNo
speciesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds data-source provenance, assembly mappings, and the fact that results include counts per species, which is useful context. It does not disclose return structure, pagination, or error behavior, so it adds some but not rich behavioral clarity beyond annotations.

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

Conciseness2/5

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

The description is dominated by a single run-on parenthetical listing data sources, assembly versions, and consortium provenance. The actual tool behavior and query example appear at the end rather than being front-loaded. Much of the assembly detail does not help an agent decide when or how to call the tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description should clearly explain what the tool returns, how counts per species are structured, and how the species parameter affects results. It gives only a high-level indication of return content and omits species-filter behavior. The extensive provenance detail does not compensate for these missing invocation-critical details.

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

Parameters2/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 compensate for both parameters. It explains that query filters trait names and gives examples, but the species parameter is never explicitly described as a filter or constrained to the long species list provided. The description therefore adds meaning for query only and leaves species semantics ambiguous.

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

Purpose3/5

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

The description indicates the tool deals with traits having QTL or GWAS results and counts per species, plus a trait-name query filter. However, it is presented as a dense provenance sentence rather than a clear verb+resource statement, and it does not distinguish this tool from siblings like legume_qtl or trait_hits. An agent can infer the purpose but must work through excessive assembly and source detail to do so.

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

Usage Guidelines2/5

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

The only usage guidance is that query filters trait names, with examples such as 'seed' and 'rust'. There is no explicit guidance on when to use this tool versus alternatives, no exclusion conditions, and no explanation of how the species parameter changes the query. The species list implies filtering but does not state when or why to supply it.

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