Skip to main content
Glama

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. Without BLAST results it returns the targets to search and says the off-target check has not been run.

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.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false, and destructiveHint=false, so safety is covered. Beyond that, the description adds real behavioral context: the exact design constraints applied, and the graceful-degradation path where a missing blast_csv yields unverified targets plus an explicit 'off-target check has not been run' notice.

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?

Purpose is front-loaded in the opening clause, followed by the rule list and the no-BLAST fallback. The single dense rule sentence is long but each clause maps to a design parameter, so it earns its place; structure is functional though heavy.

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 an output schema present, return values need no explanation, and 100% schema coverage handles parameters. The description supplies the domain ruleset and the degraded-mode behavior, making it largely self-contained for a 16-parameter tool; only explicit sibling routing is missing.

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 schema already documents all 16 parameters in detail. The description echoes several defaults (20 nt arms, 4 mismatches, 10 bp spacing) tying them to 10x rules, but adds little syntactic meaning beyond the schema. Baseline 3 is appropriate.

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 (Design), a precise resource (Xenium custom-panel padlock targets), and scope (on the subject transcript to 10x Genomics' rules CG000683). This clearly distinguishes it from the many sibling design_* probes tools (design_padlock_probes, design_merfish_probes, design_ish_probes), which an agent would otherwise confuse.

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 implies the workflow: it tells the agent that without BLAST results it only returns targets to search and flags the off-target check as not run, which signals a two-pass usage pattern. However, it never explicitly names when to choose this over the sibling probe-design tools (e.g. design_padlock_probes) or states prerequisites, leaving selection context to inference.

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