Skip to main content
Glama

find_marker

Read-onlyIdempotent

Position(s) of a genetic marker (90K/80K/9K iSelect, 35K Axiom, KASP, DArT, SSR e.g. 'BS00000713', 'wmc617', 'Xgwm149'; 40K array IDs such as 'IWB61980' or 'AVRIG14047' come from CropSNPdb) on IWGSC RefSeq v2.1 (IWGSC GMAP alignments), with genes within +/- flank bp of each hit.

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": {
      "marker": "<marker>"
    },
    "name": "find_marker"
  }
}

Input Schema

NameRequiredDescriptionDefault
flankNo
markerYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world behavior, so safety is covered. The description adds real context beyond that: the reference assembly, the alignment provenance (GMAP), and the fact that neighboring genes are returned per hit. It says nothing about behavior when a marker has no alignment, multiple hits, or how many results to expect.

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?

The core statement is front-loaded in the first clause, followed by a parenthetical catalog of supported marker platforms and the flank behavior. The dense parenthetical is justified by the ambiguity of marker IDs, and no sentence is 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?

For a two-parameter lookup tool with no output schema, the description supplies both the provenance of the coordinates and a summary of returned content. Remaining gaps — flank units/default and no-hit behavior — are modest and partly covered by the schema's own default value.

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 parameter meaning, and it does for the critical one: concrete example IDs from several array platforms clarify accepted formats far beyond `{"marker": string}`. The `flank` parameter is given implicit meaning as a base-pair window around each hit, though its units and default are never stated in the description.

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 states a specific resource and outcome: physical positions of a genetic marker on IWGSC RefSeq v2.1, plus genes within +/- flank bp of each hit. It names the alignment source (IWGSC GMAP) and enumerates accepted marker platforms, so the agent knows exactly what is returned. It does not differentiate itself from siblings such as snp_markers or genes_in_region, which keeps it from 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?

Usage is implied rather than stated: the enumerated marker types (90K/80K/9K iSelect, 35K Axiom, KASP, DArT, SSR, 40K CropSNPdb IDs) tell the agent which inputs are valid, which is a usable entry condition. There is no explicit when-to-use, when-not-to-use, or pointer to an alternative tool for related queries.

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