Skip to main content
Glama

snp_compare_lines

Read-onlyIdempotent

Compare two lines' SNP genotypes on a chromosome (optionally a region): markers compared, identical, different, % identity and the regions where they differ (useful for pedigree/introgression questions).

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": {
      "line_a": "<line_a>",
      "line_b": "<line_b>",
      "chromosome": "<chromosome>"
    },
    "name": "snp_compare_lines"
  }
}

Input Schema

NameRequiredDescriptionDefault
endNo
startNo
line_aYes
line_bYes
datasetNoBrassica napus Darmor v81
chromosomeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and open-world, so the safety profile is covered. The description adds genuine value beyond that by disclosing the shape of the result (counts of identical/different markers, percent identity, and the genomic regions of difference), which matters since there is no output schema. It says nothing about cost, runtime, or how missing data is handled, keeping it below 5.

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 sentence that front-loads the core operation and appends scope and outputs, with no filler. The line break mid-sentence is a minor formatting blemish, but nothing is redundant.

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

Completeness3/5

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

For a read-only comparison tool with six parameters, no output schema and zero schema descriptions, the description covers the operation and result shape adequately. It leaves meaningful gaps an agent would want filled: the coordinate convention for start/end (1-based? BED?), what form line_a/line_b take, and whether the dataset applies to both lines.

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 six parameters, so the description must carry the burden and largely does not. Only the start/end pair is hinted at via 'optionally a region'; line identifier format, chromosome naming conventions, and the purpose of the dataset parameter (defaulting to 'Brassica napus Darmor v81') are never explained.

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 verb and resource: comparing SNP genotypes of two named lines on a chromosome, optionally restricted to a region. It also enumerates the comparison outputs (markers compared, identical, different, % identity, differing regions), which makes the operation concrete. It does not explicitly contrast itself with siblings such as snp_lines or snp_genotypes, so it falls short of 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?

The parenthetical 'useful for pedigree/introgression questions' gives a use case, which is more than nothing. However, there is no statement of when not to use it, no prerequisites (e.g. lines must exist / be in the same dataset), and no named alternative for related tasks like inspecting a single line's genotypes.

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