Skip to main content
Glama

design_merfish_probes

Read-only

Design MERFISH encoding probes for the subject transcript: tile it into target regions, keep those whose G+C and melting temperature fall in their windows, that share no k-mer with an rRNA or tRNA, and whose k-mers occur in this gene's transcripts and nowhere else in the transcriptome; attach readout sequences that spell the gene's codeword, add the amplification primers, screen the whole oligo again, select probes that cover every on-bit evenly with least overlap, and drop probes complementary to one another.

Input Schema

NameRequiredDescriptionDefault
seedNoseed for the random draws in readout assignment and selection. Advanced.
_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 G+C of a target region (exclusive). In %.
max_tmNohighest melting temperature of a target region (exclusive). In °C.
min_gcNolowest G+C of a target region (exclusive). In %.
min_tmNolowest melting temperature of a target region (exclusive). In °C.
spacerNobases between each readout and the target. Advanced.A
trialsNoselection runs; the one with the most even on-bit coverage is kept. Advanced.
barcodeNothe gene's codeword, one 0 or 1 per bit, 1 where the bit is on.
rtrna_kNok-mer length of the rRNA/tRNA screen. 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.
probe_nmNoconcentration of each probe. In nM. Advanced.
readoutsNothe readout sequences as FASTA, one per bit, in bit order.
formamideNoformamide in the hybridization buffer. In %. Advanced.
sodium_mmNomonovalent salt of the hybridization buffer. In mM. Advanced.
t7_lengthNobases of the reverse primer lost in in vitro transcription. In nt. Only applies when reverse_primer is set. Advanced.
target_idNothe transcript to design for, by its FASTA id. Empty: the transcript whose sequence is the subject's. Advanced.
expressionNoexpression per transcript, one 'id value' line each (FPKM or TPM). Empty: every transcript weighs 1, MERFISH_probe_design's own choice without expression data. Advanced.
cross_talk_kNok-mer length of the library-wide cross-hybridization screen. Advanced.
max_rtrna_otNohighest rRNA/tRNA off-target count to keep (exclusive); 0.5 keeps only regions with none. Advanced.
specificity_kNok-mer length of the specificity and readout off-target counts. Advanced.
target_lengthNolength of each target region. In nt.
transcriptomeNoevery transcript of the organism as FASTA (RefSeq titles name the gene in their last parentheses); the subject is found in it by sequence.
forward_primerNoforward primer; its reverse complement ends the oligo. Only applies when reverse_primer is set. Advanced.
reverse_primerNoreverse primer, T7 promoter at its 5' end. Empty: no primers are added. Advanced.
min_specificityNolowest specificity to keep (exclusive): the share of a region's k-mers found only in this gene.
rtrna_referenceNorRNA and tRNA sequences as FASTA. An Ensembl ncRNA FASTA is filtered to those biotypes by its headers. Empty: the rRNA/tRNA screen does not run.
one_bit_per_probeNogive each probe copies of a single readout. Advanced.
readout_assignmentNohow each probe's on-bits are drawn: balanced keeps every on-bit equally used down the transcript. Advanced.balanced
readouts_per_probeNoreadout sequences carried by each probe, split between its two ends.
probes_per_transcriptNoprobes to select.
max_readout_ot_increaseNodrop a probe whose readouts add this many expression-weighted off-target k-mers or more (the single-molecule pipeline's check). Empty: not checked. Advanced.

Output Schema

NameRequiredDescriptionDefault
probesYesthe selected encoding probes in selection order, each with its 0-based shift, target, G+C, Tm, specificity, isospecificity, readouts, barcode and the oligo to order
reportYesthe transcript-level report: probes, probes per on-bit, the fewest on any bit, and how many could be placed without overlap before and after selection
stagesYeswhat each stage took in and kept, in pipeline order, with the reason a skipped stage did not run
orderTableYesevery probe as a Name/Sequence table for pool ordering
probeCountYeshow many encoding probes were kept
explanationYesthe derivation chain: conclusion, interpretation and machinery, generated from this run

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare read-only, non-destructive, closed-world behavior. The description adds substantial pipeline detail beyond that: tiling, G+C/Tm filtering, rRNA/tRNA and transcriptome specificity screens, readout/codeword attachment, primer addition, whole-oligo re-screening, even on-bit coverage selection, and dropping complementary probes.

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 description is front-loaded and each clause describes a meaningful step in the design pipeline, with no filler. It is a single dense run-on sentence, so structure could be improved, but the length is justified by the complexity of the tool.

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 32-parameter computational design tool with an output schema and annotations, the description gives a complete high-level workflow and the key biological filters. Optional behaviors such as skipping the rRNA/tRNA screen when no reference is supplied are left to the schema, which is acceptable given full schema coverage.

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 already names and explains all 32 parameters in detail. The description reinforces key concepts such as G+C/Tm windows, codeword readouts, primers, and k-mer screens, but it does not add parameter-level meaning beyond what the schema provides.

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 description opens with a specific verb and resource: 'Design MERFISH encoding probes for the subject transcript.' The word 'MERFISH' distinguishes it from sibling probe-design tools such as design_xenium_probes, design_hcr_probes, and design_ish_probes.

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

Usage Guidelines3/5

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

The description makes clear this is for MERFISH encoding probe design on a subject transcript, but it does not explicitly say when to use this tool versus sibling probe-design alternatives or state prerequisites/exclusions. Usage is strongly implied rather than guided.

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