Skip to main content
Glama

jean — Molecular Biology & Genomics

design_qpcr_assay

Design qPCR assays over the subject — primer pair plus hydrolysis probe, ranked by penalty, with amplicon size/GC, per-oligo Tm and whether both primers bind a single site.

Input Schema

TableJSON 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.
_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 and any DMSO or formamide that every Tm in this design is measured in. Left unset it is filled from your reaction-conditions settings, and falls back to the nearest-neighbour defaults when there are none. Advanced.
max_poly_xNolongest run of one base allowed in any oligo (primer3's POLY_X). A long run mispairs by slipping, and for a TaqMan probe a run of four or more Gs quenches the reporter. In nt. Advanced.
region_endNo0-based inclusive end. Unset = the whole sequence. Advanced.
max_resultsNohow many assays to return, best penalty first.
amplicon_maxNolongest acceptable amplicon - qPCR amplicons are short on purpose, because a short product amplifies efficiently enough for the exponential phase to be clean. In bp.
amplicon_minNoshortest acceptable amplicon. In bp.
probe_max_gcNohighest acceptable probe GC content. In %. Advanced.
probe_max_tmNoprobes above this Tm are rejected outright. In °C. Advanced.
probe_min_gcNolowest acceptable probe GC content. In %. Advanced.
probe_min_tmNoprobes below this Tm are rejected outright. In °C. Advanced.
probe_tm_optNotarget probe Tm - conventionally ~10 °C above the primers, so the probe is bound before extension reaches it. In °C.
region_startNo0-based inclusive start of the region to design in. Unset = the whole sequence; pass the selection's start to scope to it. Advanced.
primer_max_gcNohighest acceptable primer GC content. In %. Advanced.
primer_max_tmNoprimers above this Tm are rejected outright. In °C. Advanced.
primer_min_gcNolowest acceptable primer GC content. In %. Advanced.
primer_min_tmNoprimers below this Tm are rejected outright, not merely penalised. In °C. Advanced.
primer_tm_optNotarget primer Tm; the penalty ranks candidates by their distance from it. In °C.
probe_chemistryNowhat the hydrolysis probe is made of. `dna` is unmodified DNA; `lna` locks the bases named by `probe_locked_positions`, which raises the probe Tm and is how a short probe reaches the TaqMan offset over its primers. MGB and Scorpion chemistries are not offered: neither has a published nearest-neighbour parameter set to compute a Tm from.dna
structure_checkNorun the `thal` secondary-structure check on the RETURNED assays: hairpin and cross-dimer melting temperatures for all three oligos and every pairing between them. On by default, because a qPCR assay that dimerises is the commonest design failure and penalty ranking alone will happily put one first. Off returns null structures and is measurably faster - the check is a dynamic-programming alignment per oligo pair. Advanced.
probe_max_lengthNolongest probe considered. In nt. Advanced.
probe_min_lengthNoshortest probe considered. In nt. Advanced.
probe_opt_lengthNoprobe length the penalty prefers. In nt. Advanced.
primer_max_lengthNolongest primer considered; primer3's own ceiling is 36. In nt. Advanced.
primer_min_lengthNoshortest primer considered. In nt. Advanced.
primer_opt_lengthNoprimer length the penalty prefers. In nt. Advanced.
probe_tm_offset_minNohow many °C the probe Tm must exceed the MEAN primer Tm. TaqMan guidance is 8-10; below that the probe can melt off before it is cleaved. In °C.
probe_locked_positionsNowhich bases to lock, 1-based from the probe's 5′ end, e.g. `3, 6, 9`. Read only when `probe_chemistry` is `lna`. Positions must be interior to the SHORTEST probe the search will try and never adjacent, because McTigue et al. (2004) measured one locked base per nearest neighbour and none at a duplex end - a position that breaks either rule is refused by name rather than silently dropped. Only applies when probe_chemistry is lna.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
bestYesthe best-penalty assay
countYeshow many assays were found
probeYesthe best assay's probe
assaysYesthe ranked assays
offsetYeswhere the designed-in stretch starts in the record: add it to every position above for record coordinates. 0 unless a region was given
forwardYesthe best assay's forward primer
reverseYesthe best assay's reverse primer
conditionsYesthe buffer every Tm in this design was measured in - salt, magnesium, dNTPs, oligo concentration, the salt-correction method and any additives - or a note saying none were supplied
probe_orderedYesthe best assay's probe as it must be ORDERED: plain DNA, or the locked-base notation (`GTCGLAAC`) when the probe was designed as LNA

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 declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, and the description neither contradicts nor elaborates on those. It adds useful behavioural detail about the ranking penalty and the single-site binding test, but says nothing about side effects, compute cost, or that structure_check materially changes runtime (only the schema does that).

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 dense sentence built on em-dashes that front-loads the action (design qPCR assays) and then the output shape. Every clause carries information, though the phrasing is compact enough to read as a spec fragment rather than prose.

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 29-parameter design tool with an output schema present, the description covers purpose and result shape adequately, and the schema carries the parameter burden. What is missing is selection context: nothing tells the agent when this assay designer beats the sibling primer/probe designers, which is the main decision it faces.

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 100% across 29 parameters, and the schema descriptions are unusually thorough (units, defaults, TaqMan rationale, interaction rules such as DMSOfactor overriding dmsoMethod). The prose description adds no parameter-level meaning, so the baseline 3 applies.

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+resource (design qPCR assays) and pins down the artifact produced: primer pair plus hydrolysis probe, ranked by penalty, with amplicon size/GC and per-oligo Tm. That differentiates it from generic siblings like design_primers or design_primer_pairs, though no sibling is named explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no stated prerequisites (e.g. that a subject record is required), and no routing away from the many adjacent probe/primer designers (design_hcr_probes, design_padlock_probes, design_scorpion_stem, check_primer_specificity). The agent must infer applicability from the tool name alone.

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