Skip to main content
Glama

jean — Molecular Biology & Genomics

design_lamp_primers

Design LAMP (loop-mediated isothermal amplification) primer SETS - four core oligos (F3 · B3 · FIP · BIP) plus optional loop primers, judged against Eiken's own PrimerExplorer V5 criteria. Not a pair: LAMP needs six binding regions in the published order and the distances BETWEEN them are as much of the design as the oligos. Each set comes back with the arithmetic behind its rank.

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.
gc_maxNoGC FRACTION window, 0-1 (manual §2.3: "between about 40% to 65%") - upper bound. Unset = the preset for this template's GC class. Advanced.
gc_minNoGC FRACTION window, 0-1 (manual §2.3: "between about 40% to 65%") - lower bound. Unset = the preset for this template's GC class. Advanced.
_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.
max_setsNohow many sets to return, best first.
length_maxNolength window for the outer/inner binding regions (manual §4.2) - upper bound. Unset = the preset for this template's GC class. In nt. Advanced.
length_minNolength window for the outer/inner binding regions (manual §4.2) - lower bound. Unset = the preset for this template's GC class. In nt. Advanced.
region_endNo0-based inclusive end. Unset = the whole sequence. Advanced.
tm_loop_maxNoTm window for the loop primers LF / LB - upper bound. Unset = the preset for this template's GC class. In °C. Advanced.
tm_loop_minNoTm window for the loop primers LF / LB - lower bound. Unset = the preset for this template's GC class. In °C. Advanced.
loop_primersNodesign LF/LB as well. They are optional in LAMP and accelerate the reaction.
region_startNo0-based inclusive start of the region to design into (LAMP designs into a stretch, not a whole plasmid). Unset = the whole sequence; pass the selection's start to scope to it. Advanced.
tm_inner_maxNoTm window for F1c / B1c - the manual's "about 65 °C" - upper bound. Unset = the preset for this template's GC class. In °C. Advanced.
tm_inner_minNoTm window for F1c / B1c - the manual's "about 65 °C" - lower bound. Unset = the preset for this template's GC class. In °C. Advanced.
tm_outer_maxNoTm window for F2 / B2 / F3 / B3 - the manual's "about 60 °C" - upper bound. Unset = the preset for this template's GC class. In °C. Advanced.
tm_outer_minNoTm window for F2 / B2 / F3 / B3 - the manual's "about 60 °C" - lower bound. Unset = the preset for this template's GC class. In °C. Advanced.
loop_span_maxNo5' of F2 to 5' of F1 - the portion that forms the loop (manual §2.5: 40-60) - upper bound. Unset = the preset for this template's GC class. In bp. Advanced.
loop_span_minNo5' of F2 to 5' of F1 - the portion that forms the loop (manual §2.5: 40-60) - lower bound. Unset = the preset for this template's GC class. In bp. Advanced.
outer_gap_maxNoF3 to F2 and B3 to B2 gap. THE TWO AUTHORITIES DISAGREE here too: PrimerExplorer V5 says 0-60, the Eiken genome site 0-20 - upper bound. Unset = the preset for this template's GC class. In bp. Advanced.
outer_gap_minNoF3 to F2 and B3 to B2 gap. THE TWO AUTHORITIES DISAGREE here too: PrimerExplorer V5 says 0-60, the Eiken genome site 0-20 - lower bound. Unset = the preset for this template's GC class. In bp. Advanced.
end_stability_dgNothe terminal-6-base stability rule (manual §2.2: the ΔG "is -4 kcal/mol or less"). In kcal/mol. Advanced.
end_stability_ntNohow many terminal bases the end-stability rule measures (manual §2.2: 6). In nt. Advanced.
amplified_span_maxNoF2 5' to B2 5', the amplified region. THE TWO AUTHORITIES DISAGREE: PrimerExplorer V5 says 120-160, the Eiken genome site 120-180; the default follows PrimerExplorer and this is the knob for the other reading - upper bound. Unset = the preset for this template's GC class. In bp. Advanced.
amplified_span_minNoF2 5' to B2 5', the amplified region. THE TWO AUTHORITIES DISAGREE: PrimerExplorer V5 says 120-160, the Eiken genome site 120-180; the default follows PrimerExplorer and this is the knob for the other reading - lower bound. Unset = the preset for this template's GC class. In bp. Advanced.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
b3Yesthe best set's B3 outer primer
f3Yesthe best set's F3 outer primer
bipYesthe best set's BIP (B1c + B2), as ordered
fipYesthe best set's FIP (F1c + F2), as ordered
setsYesthe primer sets, best first: six regions in the literature order with every measurement that decided each one
offsetYeswhere the designed-in stretch starts in the record: add it to every position above for record coordinates. 0 unless a region was given
setCountYeshow many sets were found
constraintsYesevery window the search actually ran under, so a readout never has to restate them or guess which preset applied
targetClassYeswhich preset the search ran under - atRich, normal or gcRich, chosen from the template's own GC content (manual §4.3)
penaltyTermsYeswhat the best set's rank is MADE OF - one entry per criterion with the value measured, the window it was judged against and its cost. The costs sum to the penalty

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, so the write/safety profile is covered. The description adds that 'each set comes back with the arithmetic behind its rank' and that criteria follow Eiken PrimerExplorer V5, which is useful context, but it never states the design defaults, that no parameters are required, or what happens when a region is and isn't scoped.

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?

Three sentences, front-loaded with verb+resource and the anti-sibling clause before the return-value note; nothing is padding, though the middle sentence's methodology aside is slightly long for the value it adds.

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, 100% schema coverage, and annotations supplying the safety profile, the description needn't explain return shape. It conveys the domain framing (LAMP vs pair, six regions, rank-with-arithmetic) an agent needs to select it, though it could say more about defaults and region scoping for a 24-param 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 100%, so the 24 parameter descriptions (GC windows, Tm windows, span constraints, region scoping, the authority disagreements) fully carry semantics. The description only gestures at 'the distances BETWEEN them' without adding format or default detail, so the baseline 3 is correct.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource (design LAMP primer sets), names the exact oligos produced (F3/B3/FIP/BIP plus optional loops), and explicitly distinguishes itself from pair design ('Not a pair'), so an agent can separate it from design_primer_pairs without opening any schema.

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

Usage Guidelines4/5

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

The 'Not a pair: LAMP needs six binding regions' clause routes the agent away from the PCR-pair sibling and toward LAMP-specific needs, which is clear context. It stops short of naming an explicit alternative or a when-not-to-use condition, so it misses the top band.

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