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
datasetNoBrassica napus Darmor v81
chromosomeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and openWorld behavior. The description adds that results include marker IDs, positions, and total count, but does not explain pagination, limit behavior, or dataset scope.

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

Conciseness5/5

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

A single compact sentence with the resource and return scope front-loaded; every phrase contributes useful information without waste.

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, no output schema, and zero parameter descriptions, the one-sentence description is too sparse for complete invocation. It mentions the returned content, which prevents a 1, but omits limit/pagination semantics, dataset scope, and alternative routing.

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% across five parameters. The description only implies chromosome/start/end as the region and does not explain limit, dataset, or the default dataset value, so it fails to compensate for the schema gap.

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) and return content (IDs, positions, total count) scoped to a region, so the agent knows this is a regional marker lookup. It does not explicitly differentiate this from sibling tools such as snp_genotypes or snp_haplotype_carriers, keeping it below 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 phrase 'in a region' implies this tool is for regional SNP marker queries, but the description gives no explicit when-to-use guidance, prerequisites, or alternatives. Usage is inferable from the resource and scope, not actively routed.

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