Skip to main content
Glama

jean — Molecular Biology & Genomics

design_bisulfite_primers

Design BSP or MSP primers for a methylation assay, on the CONVERTED strands: after bisulfite treatment every unmethylated C reads as T, which is a different template from the one every other designer sees. BSP primers avoid CpGs so they amplify regardless of methylation state; MSP primers sit ON CpGs so they discriminate. Also reports the CpG islands (EMBOSS cpgplot) the assay should target.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
assayNoBSP = bisulfite sequencing PCR: primers avoid CpG sites so both methylated and unmethylated template amplify equally, and the methylation is read from the SEQUENCE afterwards. MSP = methylation-specific PCR: primers cover CpG sites so amplification ITSELF is the readout. They answer different questions and are not interchangeable. Values: BSP (BSP - amplify regardless of methylation), MSP (MSP - amplify only one state).BSP
_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.
max_gcNohighest acceptable GC. In %. Advanced.
max_tmNoprimers above this Tm are rejected outright. In °C. Advanced.
min_gcNolowest acceptable GC. The floor is low on purpose: after conversion every unmethylated C is a T, so converted DNA is genuinely GC-poor and an ordinary 40% floor rejects correct primers. In %. Advanced.
min_tmNoprimers below this Tm are rejected outright. In °C. Advanced.
opt_tmNotarget Tm; candidates rank by distance from it. Bisulfite-converted DNA is C-poor, so these run lower than an ordinary design. In °C.
min_cpgNoMSP ONLY. The fewest CpG sites a primer must cover, so it can discriminate methylated from unmethylated at all. In sites.
_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.
criteriaNowhich published criteria call a CpG island: Gardiner-Garden & Frommer 1987 as EMBOSS cpgplot encodes it, or the stricter Takai & Jones 2002, which excludes most Alu repeats. Values: cpgplot (Gardiner-Garden & Frommer (cpgplot)), takaiJones (Takai & Jones 2002 (promoter islands)).cpgplot
max_lengthNolongest primer considered. In nt. Advanced.
min_lengthNoshortest primer considered. In nt. Advanced.
opt_lengthNoprimer length the ranking prefers. In nt.
region_endNo0-based inclusive end. Unset = the whole sequence. Advanced.
max_resultsNohow many primer pairs to return, best first.
product_maxNolongest acceptable amplicon. In bp.
product_minNoshortest acceptable amplicon. In bp.
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.
island_windowNosliding window over which C, G and CpG are counted (cpgplot -window); unset takes the preset's. In bp. Advanced.
min_non_cpg_cNoBSP ONLY. The fewest non-CpG cytosines the ORIGINAL sequence under a primer must carry - the rule that makes a BSP primer bisulfite-SPECIFIC, because those cytosines become T only if conversion worked. A primer with none anneals to untreated DNA just as well and the assay silently reports on template that was never converted. In nt.
design_in_islandNodesign inside this island only, by its rank in the reported list (1 = first). Unset designs anywhere in the region; the panel instead asks for an island to be picked.
island_min_lengthNominimum island length (cpgplot -minlen); unset takes the preset's. In bp. Advanced.
island_min_obs_expNominimum observed/expected CpG (cpgplot -minoe); unset takes the preset's. Advanced.
island_min_percentNominimum %C+%G (cpgplot -minpc); unset takes the preset's. In %. Advanced.
max_cpg_distance_from_3NoMSP ONLY. How close to the 3' end the last CpG must sit. A mismatch discriminates most strongly at the 3' end, because that is where the polymerase extends. In nt. Advanced.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
assayYeswhich assay was designed, echoed so a result never has to be guessed at
countYeshow many pairs were found
pairsYesthe primer pairs, best first: each with both oligos, their coordinates on the ORIGINAL unconverted sequence, Tm, GC, CpG count and the non-CpG C conversion check
forwardYesthe best pair's forward primer (wire into pcr_amplify)
islandsYesCpG islands in the record (EMBOSS cpgplot criteria) - what a methylation assay should be aimed at
reverseYesthe best pair's reverse primer
islandCountYeshow many CpG islands were found
methylatedPairsYesMSP: the pairs specific for the METHYLATED allele. Empty under BSP
unmethylatedPairsYesMSP: the pairs specific for the UNMETHYLATED allele - the other half of the assay, and the control that tells a negative from a failed reaction. Empty under BSP

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations provide a safety profile (readOnly=false, destructive=false, openWorld=false) for a design tool, so the description's job is contextual. It adds real domain behavior: the tool operates on the converted strand, differs by BSP/MSP chemistry, and also returns CpG island calls — information beyond what the annotations convey. It doesn't elaborate on failure modes or rate limits, but the added scientific context is substantial.

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?

Verb+resource is front-loaded, followed by the biological rationale and the CpG-island output note in three tight sentences. Some biology overlaps with schema parameter text, but nothing is wasted and structure is sound.

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 25-parameter tool with nested objects and an output schema present, the description covers purpose, chemistry choice, and output scope adequately, leaning on the schema for parameter detail. Only minor gaps (no note on the nested _subject/_files handling or the Advanced-parameter grouping) keep it short of a 5.

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% and the schema descriptions are unusually rich (assay enum fully explained, min_non_cpg_c rationale spelled out). The description reinforces BSP/MSP semantics but adds no parameter detail the schema lacks, so the baseline 3 applies.

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 BSP/MSP primers) and immediately scopes it to a methylation assay on bisulfite-CONVERTED strands, explicitly noting this is 'a different template from the one every other designer sees' — which distinguishes it from siblings like design_primers, design_primer_pairs, design_qpcr_assay. An agent can tell it apart without opening the 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?

Explains the BSP-vs-MSP choice (avoid CpGs to amplify regardless of methylation vs sit ON CpGs to discriminate), giving clear in-tool routing. It does not explicitly state when to prefer this tool over an ordinary designer beyond the implicit converted-template distinction, so no explicit alternative is named, but the context is clear.

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