Skip to main content
Glama

lupin_markers

Read-onlyIdempotent

Narrow-leafed lupin (Lupinus angustifolius) genetic map: 9,972 markers (DArTseq SNP/PAV, Fluidigm SNP, indel, SSR, gene-based) and domestication loci (Tardus and Lentus pod shattering, Leucospermus white flower/seed, Iucundus low alkaloid, Mollis soft seed, Ku vernalisation independence, Lanr1 anthracnose resistance) on the 97L380 RIL map (83A:476 x P27255), with positions on the Tanjil reference (= Ensembl Plants lupinus_angustifolius, LG01-LG20) and Medicago Mt4.0 hits. Search by marker name (exact or prefix), trait words (e.g. 'alkaloid', 'pod shattering'), Tanjil region (chromosome LGxx + start/end) or map interval (chromosome + cm_start/cm_end). For trait loci and unplaced markers the physical interval comes from the nearest anchored map neighbours, with genes_in_region arguments.

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

Input Schema

NameRequiredDescriptionDefault
endNo
limitNo
startNo
traitNo
cm_endNo
markerNo
cm_startNo
chromosomeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/idempotentHint/openWorldHint, so the safety profile is covered; the description adds real behavioral content by explaining that trait loci and unplaced markers derive their physical interval from the nearest anchored map neighbours. It does not mention the default limit of 50, result ordering, or what a returned record contains.

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?

It is a single dense paragraph with the dataset identity front-loaded and the search modes following in a logical order, and nearly every clause (map name, parent cross, reference assembly, Medicago hits) carries discriminating information. It is close to over-stuffed, though nothing is genuinely redundant.

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

Completeness5/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 compensates by stating the coordinate systems results are reported on (Tanjil LG01-LG20 and Medicago Mt4.0 hits) and how unplaced markers are positioned. Combined with the explicit query modes, an agent has enough to call it correctly without guessing.

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 description coverage is 0% and no parameter is annotated, so the description carries the full burden and largely meets it: marker (exact or prefix), trait (free-text trait words with examples), chromosome (LGxx form), start/end (Tanjil coordinates) and cm_start/cm_end (map interval) all get meaning plus pairing rules. Only limit is left unexplained, and numeric formats for the coordinate bounds are implied rather than stated.

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?

The description names a specific resource ('Narrow-leafed lupin genetic map', 9,972 markers) and a specific action (search by marker name, trait, region or map interval), and enumerates the marker classes and named domestication loci included. It is clearly distinguishable from siblings such as genes_in_region, trait_hits or legume_qtl without opening any schema.

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 spells out four concrete query modes and the argument combinations that trigger each: exact/prefix marker name, trait words such as 'alkaloid' or 'pod shattering', chromosome LGxx plus start/end, and chromosome plus cm_start/cm_end. It also points at genes_in_region for downstream interval use. It stops short of stating when not to use this tool or naming a sibling to prefer for a non-lupin species.

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