Skip to main content
Glama

jean — Molecular Biology & Genomics

design_knockout_package

The complete build package for a knockout or knock-in, as one object: guides inside the target, an off-target census for the chosen one within this molecule, a repair template with real homology arms, a screening PCR whose primers sit OUTSIDE the arms, the protocol in order, the fragments and oligos to buy, and every coordinate ready for the map. Two donor modes: by default the arms sit on the cut (a point insertion — the target's own sequence is kept on both sides), and with replace_target the arms flank the whole target and it is deleted, which is the mode for replacing one CDS with another (an empty insert then deletes the target cleanly). It refuses rather than guessing: no PAM in the target, arms that run off a linear molecule, a screening amplicon that cannot clear the arms, or a non-DNA insert; and in the default mode it WARNS when an insert lands inside the target, because that is a fusion rather than a replacement. Arm length, screening flank and guide count are yours to state, because each follows the delivery method and the organism.

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.
guidesNohow many guides to carry into the package, best-scoring first. The rest are the alternatives, not filler.
insertNosequence to place at the cut (a tag, a selection cassette). Leave empty for a scarless rejoin — the package then WARNS that the two screening products are the same length.
subjectNothe molecule to edit — wire a record or name a library document; leave unset to edit the open record.
_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.
nucleaseNothe nuclease (PAM + spacer length) to scan the target for. Values: SpCas9 (SpCas9: NGG (3')), SpCas9-NG (SpCas9-NG: NG (3')), SpG (SpG: NGN (3')), SpRY (SpRY: NRN (3')), xCas9 (xCas9: NG (3')), SaCas9 (SaCas9: NNGRRT (3')), SaCas9-KKH (SaCas9-KKH: NNNRRT (3')), AsCas12a (AsCas12a: TTTV (5')), LbCas12a (LbCas12a: TTTV (5')), enAsCas12a (enAsCas12a: TTTV (5')).SpCas9
primer_tmNotarget melting temperature for the screening primers [°C] — follows your polymerase and buffer. In °C. Advanced.
arm_lengthYeshomology-arm length on EACH side of the cut, in bp. A protocol decision that follows the delivery method, so there is no default: state what yours needs. The published working range is 100-800 (100-400 nt synthetic, up to ~800 bp cloned). In bp.
target_endYesend of the gene to knock out (0-based, exclusive). In bp.
insert_nameNowhat the insert is called in the protocol and on the order form.
target_nameNowhat the target is called, so every mark, primer and order line names its subject.target
screen_flankYeshow far OUTSIDE the arms the screening primers must bind, in bp. Not decoration: a primer inside the arms amplifies the repair template as readily as the locus, so the assay cannot tell an edited colony from plasmid carry-over. In bp.
target_startYesstart of the gene to knock out (0-based, inclusive). In bp.
max_mismatchesNomismatch ceiling for the off-target search within this molecule. Advanced.
replace_targetNoreplace the WHOLE target region with the insert, arms flanking the target — the gene-replacement donor. Off (default): the arms sit on the cut and the target's own sequence is kept on both sides of the insert (a point insertion), so this must be ON to knock one CDS in for another. Empty insert + this = a clean deletion of the target. Advanced.
restriction_enzymesNocloning enzymes whose recognition site must NOT appear in a spacer. Advanced.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
donorYesthe repair template: both arms with their genomic spans, the insert, and the junctions to sequence across
marksYesevery span this package names, ready for the map
orderYesthe fragments and oligos to buy, each with the design decision it comes from
stepsYesthe protocol in the order it is done
chosenYesthe guide the package was built around
guidesYesevery guide inside the target, scored, best first
recordYesthe repair template as a sequence record, so the run leaves the user holding the thing to order
reportYesthe whole package as Markdown — protocol, order form, guides, template, screening and marks — so it survives outside the transcript
screeningYesthe screening PCR: the pair, the two product lengths, and the span they cover
offTargetsYesthe off-target census for the chosen spacer WITHIN this molecule, with the scope stated

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

With annotations only stating readOnlyHint=false / destructiveHint=false / openWorldHint=false, the description carries substantial extra behavioral weight: it discloses four hard refusal conditions (no PAM, arms running off a linear molecule, un-clearable screening amplicon, non-DNA insert) and two warning behaviors (insert landing inside the target in default mode; identical-length screening products for a scarless rejoin). That is precisely the failure-mode disclosure an agent needs before calling.

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?

The purpose and package contents are front-loaded in the first sentence, and the mode semantics, refusal cases, and required choices follow in a logical order. The prose is dense and runs long (~200 words in one block), but each sentence contributes a distinct behavioral or parameter fact rather than filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists (so return values need not be explained), annotations cover the safety profile, and the schema fully documents all 16 parameters. The description closes the remaining gaps — donor mode semantics, refusal/warning behavior, and which parameters are user-decided — leaving nothing an agent needs to call the tool correctly.

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 baseline is 3. The description' Explanation of `replace_target` is nearly verbatim the schema's own wording, so it mostly duplicates structured data; its only additive value is the framing that arm_length, screen_flank and guide count are user-stated protocol decisions rather than defaults.

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?

The first sentence names the specific verb+resource ('the complete build package for a knockout or knock-in') and then enumerates exactly what the single object contains — guides, off-target census, repair template, screening PCR, protocol, fragments/oligos, coordinates. This distinguishes it from sibling design tools such as crispr_design_guides or design_gibson_primers without requiring the agent to open a 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 description gives clear situational guidance: use the default mode for a point insertion and set `replace_target` 'to knock one CDS in for another', and it explains when an empty insert yields a clean deletion. It also enumerates refusal conditions. However, it never names an alternative sibling tool (e.g., crispr_design_guides for guides-only work), so routing is described by condition rather than by explicit alternative.

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