Skip to main content
Glama

watkins_compare_groups

Read-onlyIdempotent

Genes whose presence frequency differs most between two sets of Watkins accessions. group_a / group_b as ':' with field one of group (ancestral group), country, continent, growth_habit, e.g. 'group:AG3' vs 'group:Modern', 'country:India' vs 'country:China'. min_diff is the minimum absolute frequency difference (0-1). Negative diff = more common in group_b.

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": {
      "group_a": "<group_a>",
      "group_b": "<group_b>"
    },
    "name": "watkins_compare_groups"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
group_aYes
group_bYes
min_diffNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish that this is a safe, idempotent, open-world read, so the description is free to spend its words elsewhere — and it does, disclosing the ranking behaviour, the sign convention ('Negative diff = more common in group_b'), and the min_diff threshold range. Return shape and whether results are truncated at limit remain unstated.

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?

Purpose is front-loaded in one sentence, followed by format rules, examples, and the arithmetic convention — no filler. The glyph/format paragraph is slightly dense, but every sentence carries operational information.

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 four-parameter comparison tool with no output schema, the description supplies the format contract, the threshold semantics, and the interpretation of the result sign, which is enough to call it correctly. An agent would still have to guess what a result row contains and what limit truncates.

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 the parameters, and it does so for the two required ones with an explicit grammar, a closed field list, and worked examples, plus the range and meaning of min_diff. The limit parameter (default 50) is never mentioned, which is the one remaining hole.

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 first sentence names a specific operation on a specific resource: genes ranked by presence-frequency difference between two sets of Watkins accessions. That is far more informative than the bare name, though it never explicitly contrasts itself with near neighbours such as watkins_gene_presence or snp_compare_lines.

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 mechanics are well covered: the '<field>:<value>' convention, the enumerable fields (group, country, continent, growth_habit), and concrete paired examples make it obvious how to invoke. What is missing is selection guidance — when to reach for this comparison instead of a single-gene presence lookup or the SNP comparison sibling.

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