Skip to main content
Glama

assemble_index_oligos

Read-only

Turn index sequences into the oligos a synthesiser makes: each index spliced between 5'/3' adapter arms, or onto a PCR primer in either orientation with an optional spacer.

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.
formatNoadapter arms around the index, or a tagged PCR primer. Values: adapter (5'/3' adapter arms), primer (Tagged PCR primer).adapter
primerNothe PCR primer the tag is appended to — required when `format` is `primer`.
spacerNobases between the tag and the primer. Heterogeneity/phasing spacers are routine on a low-diversity library. 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.
barcodesYesthe index sequences to assemble.
adapter_3No3' arm the index is spliced before — the TruSeq read-1 primer, and the panel's own default.ACACTCTTTCCCTACACGACGCTCTTCCGATCT
adapter_5No5' arm the index is spliced after — the Illumina P5, and the panel's own default.AATGATACGGCGACCACCGAGATCTACAC
reverse_complement_tagNouse each tag as its reverse complement, in an adapter or on a primer, as the instrument requires for some read orientations. Advanced.

Output Schema

NameRequiredDescriptionDefault
countYeshow many oligos were assembled
oligosYeseach assembled oligo with its name, sequence and length
longestYesthe longest assembled oligo, in bases — the number a synthesis quote turns on
warningsYesjunction problems that only exist once tag and oligo are joined: a run across the junction, a self-complementary 5' tetramer, an oligo over the synthesis guideline

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / reverse_complement_tag / description
      Previous value: -"append the tag as its reverse complement, as the instrument requires for some read orientations. Advanced."New value: +"use each tag as its reverse complement, in an adapter or on a primer, as the instrument requires for some read orientations. Advanced."
  2. First observed

TDQS

A3.8/5.0
Behavior1/5

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

The tool performs a synthetic/creation action ('Turn index sequences into the oligos a synthesiser makes'), which suggests a write operation. This fundamentally conflicts with the annotation 'readOnlyHint: true', misleading the agent about the tool's execution behavior.

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?

The definition is maximally concise, achieving high informational density in a single, fluid sentence. It front-loads the core function without unnecessary padding.

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?

Given the highly detailed input schema, the description is functionally complete. It tells the agent *how* the inputs are linked together to create the output, which is all that's needed for a successful call.

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?

While the input schema is 100% covered, the description provides the essential operational context for the parameters, specifically defining why the 'format' and 'adapter' fields exist and how they dictate the resulting oligo structure.

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 uses precise, technical language ('spliced between 5'/3' adapter arms' or 'onto a PCR primer') to define the exact transformation the tool performs. It clearly states its purpose: converting index sequences into functional oligos.

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?

It explicitly outlines the two primary operational modes: assembly using standard adapter arms versus assembly onto a pre-existing PCR primer. This guides the agent on the necessary input configurations.

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