Skip to main content
Glama

check_qpcr_multiplex

Read-only

Can these qPCR assays share a tube? Every unordered pair is scored on MultiPLX's five primer-primer and primer-product interactions and, beyond MultiPLX, on each assay's hydrolysis PROBE against the other assay's oligos (primer3 thal) — a probe consumed by a neighbour's primer loses signal while the PCR works perfectly, which reads as poor efficiency and is blamed on the primers.

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": {
      "assays": "<assays>"
    },
    "name": "check_qpcr_multiplex"
  }
}

Input Schema

NameRequiredDescriptionDefault
_filesNoThe project: record references shaped like _subject. Their records become library documents a tool names in sequences/parts/document; a trace or alignment is found by file name.
assaysYesthe assays to pool: one object per assay with `name`, `forward`, `reverse`, `probe` and `amplicon`. Wire `design_qpcr_assay` outputs here, or list them yourself. Without `amplicon` the two primer-product scores cannot be measured and say so.
_subjectNoThe record to act on: exactly one of sequence, accession (+source), sample (an id from list_samples) or file ({name, text} or {name, base64}); record_index picks one record of several.
conditionsNosalt, magnesium, dNTP and oligo concentrations plus the salt-correction method every interaction is measured in. Left unset it is filled from your reaction-conditions settings, and falls back to primer3's defaults when there are none. Advanced.
stringencyNowhose cutoffs decide. `primer3` judges on the Tm limits calibrated for the engine that computes them, which is what the panel opens on; the other three are MultiPLX's own presets, verbatim from cmultiplx 1.4. Values: primer3 (primer3 limits (the engine's own)), high (MultiPLX high stringency), normal (MultiPLX normal), low (MultiPLX low).primer3

Output Schema

NameRequiredDescriptionDefault
pairsYesevery unordered pair: its five MultiPLX scores, its probe interactions, the cutoffs it breaks, whether it is compatible, and why not in words
cutoffsYesthe cutoff set the verdicts were judged against, so a report says what it means by compatible
poolableYestrue when NO pair clashes, so the whole set can go in one tube. Branch a workflow on this rather than counting the rows
compatibleYesassay names that clashed with nothing — the ones that can be pooled
conflictingYesassay names involved in at least one clash

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Beyond the readOnly/non-destructive annotations, the description discloses the scoring model: all unordered pairs, five MultiPLX interaction classes, plus an extra probe-vs-neighbour-oligo term from primer3 thal that MultiPLX does not cover. It also explains the biological meaning of that extra term (signal loss misread as poor efficiency), which is genuinely non-obvious behavior.

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?

Two sentences, front-loaded with the decision question and then the method. The trailing clause about poor efficiency being blamed on primers is colorful but does earn its place by explaining why probe cross-interactions are scored; the middle is dense with nested clauses but not padded.

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?

With an output schema present, the description needn't explain return values, and it correctly focuses on the scoring model and its rationale. A reader still lacks any hint of what score magnitudes or thresholds mean, but the annotations and output schema carry most of the remaining burden.

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 coverage is 100% and the nested conditions/stringency schemas are already richly documented, so the baseline is 3. The description adds conceptual context for why the interaction model matters but no syntax or format guidance for `assays`, `conditions`, or `stringency` beyond what the schema states.

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 opening question plus 'every unordered pair is scored on MultiPLX's five primer-primer and primer-product interactions' states a specific computation on a specific resource (qPCR assays). It is clearly distinct from a multiplex assembly tool, but it never names a sibling or states the boundary explicitly.

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 framing 'Can these qPCR assays share a tube?' strongly implies the use case (deciding whether to pool assays), and the schema notes wiring design_qpcr_assay outputs in. There is no explicit when-not guidance or named alternative for downstream assembly versus compatibility checking.

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