Skip to main content
Glama

jean — Molecular Biology & Genomics

alignment_window

Read-only

Read one window of a BAM or SAM in this project: its reads, the depth across it, and what the pairs say about the library — the same window, filters and record cap the pileup draws. Wire reads into an alignment or a screen the way the pane's own hand-offs do.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
locusNothe window, as a locus string (`ctgA:1-50,001`). Unset, it is the whole of the alignment's first reference — the window the panel opens on.
_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.
min_mapqNohide reads below this mapping quality, as the pane’s Filter reads operation does. The reads are still counted — `hidden` says how many this removed.
alignmentNowhich BAM or SAM in this project, by name. Unset, it is the project's only alignment — and it refuses rather than guessing when there is more than one.
max_readsNothe record cap. More reads than this overlap the window and the result is an even SAMPLE of them, with `sampled` saying so — the pane’s own cap is the default.
hide_secondaryNodrop secondary alignments (FLAG 0x100).
hide_duplicatesNodrop reads marked as PCR or optical duplicates (FLAG 0x400).
hide_supplementaryNodrop supplementary alignments (FLAG 0x800).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
readsYesthe reads in the window after filters: name, reference, 1-based start and end, strand, MAPQ, CIGAR, TLEN and sequence — the shape an alignment or a screen takes
hiddenYesreads in the window the filters removed — 0 with an active filter is a real answer
windowYesthe window actually read, as a locus string
sampledYesmore reads overlap the window than the cap allows, so `reads` is an even sample rather than all of them
coverageYesthe depth profile as bins across the window, in order
depth_maxYesthe deepest bin
depth_meanYesmean depth across the window’s coverage bins, over ALL reads — the coverage track is full-depth, as BamView’s is, so filters do not move it
read_countYeshow many reads that is
insert_sizeYesthe |TLEN| band this library’s own proper pairs define — `min`, `max` and whether it was MEASURED here or is the untuned fallback, which is what decides whether an insert is abnormal

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false, so the safety profile is covered. The description adds some behavioral context (mirrors the pane's window/filters/cap) but does not disclose refusal conditions, cost, or sampling semantics beyond what the schema already spells out.

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

Conciseness3/5

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

Reasonably short and front-loaded with the core action, but the second sentence is opaque jargon ('the way the pane's own hand-offs do') whose meaning is not self-evident to an agent. Half the text is spent on a metaphor rather than actionable detail.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be re-explained. However, for a 9-parameter tool with nested objects, the description leaves the integration path ('wire `reads` into…') vague and does not mention what an agent should expect when the window exceeds the cap or multiple alignments exist — details present only in the schema.

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 every parameter (locus, min_mapq, max_reads, hide_* flags, alignment, _subject) is already documented in the schema. The description only gestures at 'the same window, filters and record cap the pileup draws' without adding syntax or defaults beyond that. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource — read one window of a BAM/SAM in this project — and enumerates the three outputs (reads, depth, pair/library info). It is clear what the tool does and that it mirrors the pileup pane's window, but it never names a sibling (e.g. browse_region, alignment_agreement) to disambiguate the overlapping region-inspection space.

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 closing sentence ('Wire `reads` into an alignment or a screen the way the pane's own hand-offs do') implies the downstream workflow but gives no explicit when-to-use, when-not, or named alternative relative to the many other alignment/region tools. Usage must be inferred from the pane metaphor.

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