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
datasetNowheat40k
chromosomeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world, so the safety profile is covered; the description adds value by disclosing the computed return contents (markers compared, identical, different, percent identity, differing regions), which matters because there is no output schema. It does not disclose cost, performance, or behavior when lines share no markers. Good added context beyond annotations, but not complete.

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 front-loaded sentence with the core action first and the output list and use case trailing behind it. Dense but every clause carries information; the comma-spliced list of return fields is slightly hard to parse but not wasteful.

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?

Listing the returned metrics compensates for the missing output schema, so the agent knows what to expect. However, with 6 parameters and zero schema descriptions, the unexplained dataset parameter and the absence of any precondition or failure-mode note leave the definition short of complete for a comparison tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the full burden. It implicitly covers line_a, line_b, chromosome, and the optional start/end region, but says nothing about the 'dataset' parameter or its default (wheat40k), which materially changes results. Partial compensation only.

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 gives a specific verb and resource: compare two named lines' SNP genotypes on a chromosome with an optional region. It also enumerates what the comparison produces, so the agent knows this is a pairwise genotype-diff tool rather than a lookup like snp_genotypes or snp_haplotype_carriers. It stops short of naming a sibling to avoid, so it is clear but not fully disambiguated.

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 the agent a concrete motivating scenario. There is no explicit when-not guidance, no statement about preconditions (e.g., lines must exist in the chosen dataset), and no pointer to an alternative for related queries. Usage is implied by scenario rather than spelled out.

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