Skip to main content
Glama

Jean — Molecular Biology & Genomics

design_xenium_probes

Read-only

Design Xenium custom-panel padlock targets on the subject transcript to 10x Genomics' published rules (CG000683): two 20 nt arms whose primer3 melting temperatures fall in their windows, a ligation-junction dinucleotide the Xenium ligase accepts, no run of five G in the probe, at least four mismatches across both arms to every other transcript in a BLAST search, and probes at least 10 bp apart.

Input 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.
spacingNofewest bases between two kept targets. In bp.
tm_ruleNowhich melting temperatures must fall in their windows. 10x: the full length between 68 and 82 °C or each arm between 50 and 70 °C.either
_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.
blast_csvNoblastn -outfmt 10 output for the targets FASTA this tool returns, searched against the transcriptome (not the genome) with -word_size 7 -strand plus. Without it no target is checked for off-target homology.
junctionsNoligation-junction dinucleotides to accept, from 10x's empirical ligase preferences; 10x strongly recommends avoiding the nonpreferred four.preferred and neutral
max_g_runNolongest run of G the probe may carry; 10x: avoid five or more. Advanced.
arm_lengthNolength of each arm; the target is twice this. 10x's arms are 20 nt, shorter only for a short target whose Tm stays in range. In nt. Advanced.
max_arm_tmNohighest Tm of each arm (inclusive). In °C.
min_arm_tmNolowest Tm of each arm (inclusive). In °C.
prefer_cdsNorank targets inside the subject's CDS feature before the untranslated regions, as 10x advises where possible.
max_full_tmNohighest Tm of the whole target (inclusive). In °C.
min_full_tmNolowest Tm of the whole target (inclusive). In °C.
min_mismatchesNofewest mismatches across both arms an off-target hit must carry for the target to be kept; gaps and unaligned ends count. Only applies when blast_csv is set.
gene_accessionsNocomma-separated accessions (no version) that are this gene, its isoforms included: hits to them are not off-targets. Empty: the subject's name. Only applies when blast_csv is set.
probes_per_geneNotargets to keep; 10x's predesigned panels use eight per gene.

Output Schema

NameRequiredDescriptionDefault
probesYesthe kept targets, each with its 0-based start, target (mRNA sense), probe (its reverse complement), arm and full-length Tm, junction and its class, and the fewest off-target mismatches. Null until `blast_csv` is given
stagesYeswhat each rule took in and kept, in order, with the reason a skipped check did not run
probeCountYeshow many targets were kept. Null until `blast_csv` is given
explanationYesthe derivation chain: conclusion, interpretation and machinery, generated from this run
targetsFastaYesthe targets that pass the Tm, junction and G-run rules as FASTA, named xenium_<1-based start>, for blastn

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, non-destructive, closed-world), so the description's job is to disclose how the design behaves — and it does, enumerating the arm structure, Tm windows, junction dinucleotide rules, poly-G limit, mismatch threshold and spacing floor. It stops short of saying what the result contains or how many targets come back, but the output schema carries that.

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?

One long but front-loaded sentence: the action and target come first, then the rule set in a parallel list. Dense but nearly every clause carries a distinct constraint; the trailing 'probes at least 10 bp apart' could have been merged more tightly, and the sentence is long enough to be hard to scan.

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 16-parameter design tool with a full output schema, the description conveys the core algorithm and its external dependency on a BLAST search. What is missing is the operational sequencing (the targets FASTA must be BLASTed and fed back as blast_csv) and the fact that off-target filtering is silently skipped without it.

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 coverage is 100% and every one of the 16 parameters is documented in the schema, so the baseline is 3. The description usefully ties several defaults back to 10x guidance (20 nt arms, four mismatches, 10 bp spacing, avoid five G), but it says nothing about tm_rule, junctions, prefer_cds, gene_accessions or the _subject/_files plumbing.

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 verb and resource — 'Design Xenium custom-panel padlock targets on the subject transcript' — and anchors it to a published standard (10x CG000683), which separates it from design_padlock_probes, design_merfish_probes, design_ish_probes and design_hcr_probes without needing to name them.

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

Usage Guidelines2/5

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

The text lists design constraints but never states when an agent should pick this tool over the many sibling probe-design tools, nor any prerequisite such as supplying blast_csv before off-target filtering can occur. Usage is only inferable from the word 'Xenium' and the mention of a BLAST search.

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