Skip to main content
Glama

snp_markers

Read-onlyIdempotent

SNP array markers (IDs and positions) in a region, with the total count.

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

Input Schema

NameRequiredDescriptionDefault
endYes
limitNo
startYes
datasetNowheat40k
chromosomeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds that the response includes marker IDs, positions, and a total count, which is useful given no output schema, but it omits the default result cap (limit=200) and the dataset default, both of which affect results.

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?

A single economical sentence that front-loads the resource and return shape with no filler. Nothing wasteful, though it is perhaps too terse for a five-parameter 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?

With five parameters, 0% schema description coverage, and no output schema, the description should explain coordinate units, the limit semantics, and the dataset option. Instead it covers only the region scope and return fields, leaving real gaps for an agent attempting to call it correctly.

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 carry the burden of parameter meaning. It implies the region concept behind chromosome/start/end but says nothing about coordinate units, what limit does, or what dataset values are valid (default wheat40k), leaving two of five parameters unexplained.

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 resource (SNP array markers), the returned content (IDs and positions), a scope (in a region), and an aggregate (total count). It is clear what the tool does, though it doesn't differentiate itself from siblings like snp_genotypes or snp_lines by name.

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?

There is no statement of when to use this versus alternatives. An agent cannot tell from the description whether to prefer this over snp_genotypes, snp_lines, or genes_in_region when looking up markers in a region.

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