Skip to main content
Glama

design_indel_primers

Read-only

Round-the-horn (NEB Q5-style) primers that DELETE, INSERT or REPLACE whole residues of a CDS: the two back-to-back primers, the edited product they make after KLD re-circularisation, and the span they edit on the template. design_mutagenesis_primers covers substitutions; this covers the other three.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "design_indel_primers"
  }
}

Input Schema

NameRequiredDescriptionDefault
editNowhich edit this is. Values: delete (Delete residues), insert (Insert residues), replace (Replace residues).delete
_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.
circularNothe template is circular, which round-the-horn assumes. Taken from the record when one is open.
templateNothe whole plasmid to amplify. Left empty the open record is used, which is the usual case. Advanced.
tm_modelNoTm scale the arms are grown against. Values: santalucia (SantaLucia nearest-neighbor (Biopython Tm_NN defaults)), wallace (Wallace rule (4 °C per G·C, 2 °C per A·T)), gc:Chester_1993 (GC formula: Marmur-Doty (Chester & Marshak 1993)), gc:QuickChange (GC formula: QuikChange (the kit manufacturer’s own formula)), gc:Schildkraut_1965 (GC formula: Schildkraut & Lifson 1965 (Marmur-Doty + log[Na⁺])), gc:Wetmur_Melting_1991 (GC formula: Wetmur 1991, DNA (MELTING 4.3 approximate mode)), gc:Wetmur_RNA_1991 (GC formula: Wetmur 1991, RNA), gc:Wetmur_DNA_RNA_1991 (GC formula: Wetmur 1991, RNA/DNA hybrid), gc:Primer3 (GC formula: Primer3Plus product Tm (Biopython’s default set)), gc:Ahsen_2001 (GC formula: von Ahsen 2001 (accuracy against ease of use)).santalucia
target_tmNoannealing Tm each arm is designed to. NEB's Q5 protocol targets ~60 °C. In °C.
cds_offsetNo0-based offset of the CDS start within the template, when `template` is given literally. Resolved from the record otherwise. Advanced.
cds_featureNothe annotated CDS the residue numbers count in, by NAME. Left empty the selection scopes it, and `cds_offset` is taken from the region.
last_residueNo1-based last residue to remove, inclusive. Only applies when edit is delete or replace.
after_residueNoinsert after this residue; 0 inserts before the first. Only applies when edit is insert.
first_residueNo1-based first residue to remove (delete and replace). Only applies when edit is delete or replace.
insert_codonsNothe residues to introduce, as DNA codons in frame. A length that is not a multiple of 3 is refused rather than frameshifting the rest of the protein. Only applies when edit is insert or replace.

Output Schema

NameRequiredDescriptionDefault
kindYeswhat the engine classified this as: deletion, insertion or replacement
forwardYesthe forward primer: `seq` as ordered (5' tail + arm), `anneal` (the template-complementary part), its Tm, GC and binding span
productYesthe edited molecule these primers produce after amplification and KLD re-circularisation — wire it into a digest, a gel or a map
reverseYesthe reverse primer, same shape
editSpanYesthe span edited on the ORIGINAL template, 0-based half-open. Empty for a pure insertion, which removes nothing
deletedLengthYesbases removed
insertedLengthYesbases added

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and closed-world, so the design-only, non-mutating nature is covered structurally. The description adds the KLD re-circularisation context that explains why back-to-back primers are produced, but it does not disclose failure conditions such as non-multiple-of-3 codon lengths or arm-length limits — those live only in the parameter schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, both earning their place: the first front-loads the method and the edit types plus the outputs, the second is a one-line disambiguation. No filler or restatement of the title.

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 13 parameters, a full output schema and annotations present, the description needs only to establish scope and sibling routing, which it does. The heavy lifting on parameter behaviour is delegated correctly to a 100%-covered schema, leaving only a minor gap around preconditions and edit-size limits.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/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, and the description lifts it slightly by tying the tool to whole-residue, CDS-relative numbering ('whole residues of a CDS'), which frames why first_residue/last_residue/after_residue are residue-indexed. It adds no further guidance on the advanced template/cds_offset parameters.

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?

Names a specific method and resource ('Round-the-horn (NEB Q5-style) primers') and states the operation set precisely: DELETE, INSERT or REPLACE whole residues of a CDS. It also names what it returns (the two back-to-back primers, the edited product, the edited span), which no sibling description in the list implies.

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?

Explicitly routes substitutions away to design_mutagenesis_primers and claims the remaining three edits for itself, which is the exact decision an agent faces among the primer-design siblings. It stops short of saying when round-the-horn is inappropriate (e.g. very large edits where Gibson/fusion approaches win), so it is clear guidance without exclusions beyond the one named.

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