Skip to main content
Glama

read_sequencing_qc

Read-only

Read the QC files a sequencing provider returns alongside the reads: a per-base COVERAGE table, or a Plasmidsaurus summary (k-mer composition and the contamination estimate with its named source). These are the numbers that say whether a disappointing read is the clone's fault or the run's — a base called wrong under 3x coverage is a sequencing problem, not a cloning one. For a coverage table it also measures the track's SHAPE, because a mean has none: a run averaging 200x with one uncovered region reads as excellent. The provider states one number and two shapes — 20x for an accurate consensus, and a large gap or a sudden large increase meaning an assembly issue or a mixture of plasmid species — so the longest stretch under the line and the largest change in level are both measured and located. How large is large is NOT a number they publish, and none is invented here: the shapes are reported and the call is the reader's.

Input Schema

NameRequiredDescriptionDefault
kindNowhich report this is; `auto` sniffs it. Values: auto (Detect from the contents), perbase (Per-base coverage table), plasmidsaurus (Plasmidsaurus summary).auto
textYesthe file's contents — a per-base coverage TSV (pos / ref / reads_all), or the provider's summary text.
_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.
step_windowNopositions either side of a boundary whose MEDIAN depth is compared, when looking for a sudden change in level. A median over a window rather than two adjacent positions, so one spike is not a step and a real change in level is. Advanced.
coverage_lineNothe depth a position must reach to count as well covered. The default is the provider's own published line and nothing of ours; raise it for a construct you intend to publish.

Output Schema

NameRequiredDescriptionDefault
kindYeswhich report was actually read
shapeYesthe coverage track's SHAPE: its median, how many positions fall under the line and in how many separate runs, the longest such run with its coordinates and its floor, and the largest change in level with the position it is at
perbaseYesper-base coverage: positions counted, mean/min/max read depth, and how many positions reach 20x
readingYeswhat the coverage track says, generated from the profile that was measured rather than from the request, with the provider's own sentence quoted as theirs
longestGapYespositions in the longest unbroken stretch under the coverage line — the provider's first warning shape. 0 means no position falls under it; null for a Plasmidsaurus summary, which has no track
minCoverageYesthe LOWEST depth anywhere in the read — the number that decides whether a disagreement with the reference is believable. Null for a Plasmidsaurus summary, which measures no depth
depthProfileYesthe depth track drawn: the MINIMUM and the mean depth per window, with the coverage line and the track's median as rules, so a drop-out reads as a drop-out rather than being averaged away. Null for a Plasmidsaurus summary, which measures no track
plasmidsaurusYesthe whole parsed summary, including the raw text it came from
largestStepFoldYesthe largest sustained rise in depth, as a multiple — the provider's second warning shape. Branch on this rather than re-deriving it from the profile. Null when no step could be measured (a track shorter than two windows, or a Plasmidsaurus summary): a 0 is not a fold
contaminationPctYesPlasmidsaurus' contamination estimate, as a percentage. Null when the summary states none, and for a coverage table: a 0 would read as a clean run nobody measured
positionsAbove20xYespositions at 20x or better, out of the total. Null for a Plasmidsaurus summary
contaminationSourceYeswhat the provider says the contaminant IS — the half of the estimate that tells you what to do about it. Null when the summary names none, and for a coverage table

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / contaminationPct / x-unit
      Added value: +"%"
  2. Changed2 schema fields changed
    • addedOutput schema / properties / depthProfile
      Added value: +{
      +  "description": "the depth track drawn: the MINIMUM and the mean depth per window, with the coverage line and the track's median as rules, so a drop-out reads as a drop-out rather than being averaged away. Null for a Plasmidsaurus summary, which measures no track",
      +  "properties": {
      +    "mark": {
      +      "enum": [
      +        "line",
      +        "bar",
      +        "point"
      +      ],
      +      "type": "string"
      +    },
      +    "rules": {
      +      "items": {
      +        "properties": {
      +          "label": {
      +            "type": "string"
      +          },
      +          "y": {
      +            "type": "number"
      +          }
      +        },
      +        "required": [
      +          "y",
      +          "label"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "series": {
      +      "items": {
      +        "properties": {
      +          "name": {
      +            "type": "string"
      +          },
      +          "y": {
      +            "items": {
      +              "type": [
      +                "number",
      +                "null"
      +              ]
      +            },
      +            "type": "array"
      +          }
      +        },
      +        "required": [
      +          "name",
      +          "y"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "title": {
      +      "type": "string"
      +    },
      +    "x": {
      +      "items": {
      +        "type": "number"
      +      },
      +      "type": "array"
      +    },
      +    "xLabel": {
      +      "type": "string"
      +    },
      +    "yLabel": {
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "x",
      +    "series",
      +    "xLabel",
      +    "yLabel"
      +  ],
      +  "type": [
      +    "object",
      +    "null"
      +  ]
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "kind",
      -  "perbase",
      -  "minCoverage",
      -  "positionsAbove20x",
      -  "contaminationPct",
      -  "contaminationSource",
      -  "plasmidsaurus",
      -  "shape",
      -  "longestGap",
      -  "largestStepFold",
      -  "reading"
      -]New value: +[
      +  "kind",
      +  "perbase",
      +  "minCoverage",
      +  "positionsAbove20x",
      +  "contaminationPct",
      +  "contaminationSource",
      +  "plasmidsaurus",
      +  "shape",
      +  "longestGap",
      +  "largestStepFold",
      +  "depthProfile",
      +  "reading"
      +]
  3. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered; the description goes well beyond by disclosing what is actually computed (longest stretch under the coverage line, largest change in level, both measured and located) and the epistemic stance that thresholds are not invented. That is meaningful behavioral context an agent cannot get from the annotations.

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?

Front-loaded with purpose, then motivation, then the epistemic caveat – a sensible order with no wasted preamble. Some rhetorical phrasing ('a mean has none') costs a little compactness across a fairly long block.

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?

Output schema carries return values and annotations carry safety, so the description need only cover intent and interpretation, which it does thoroughly. It is silent on the nested _files/_subject project-reference parameters, a real gap for a tool with nested object inputs.

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?

Schema description coverage is 100%, so baseline is 3; the description adds interpretive meaning by explaining why a mean is insufficient and how the coverage line and shape measures relate to the provider's stated criteria. It does not address _files/_subject, but coverage_line and step_window get real semantic context.

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?

Opens with a specific verb and resource: reads QC files a provider returns, naming the two supported forms (per-base coverage table, Plasmidsaurus summary with k-mer composition and contamination source). An agent immediately knows what they get. It never names the nearby tools (fastq_qc, verify_read, compare_reads_to_reference), so the distinction from siblings is left implicit, which holds it below a 5.

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?

Gives a clear diagnostic trigger – 'these are the numbers that say whether a disappointing read is the clone's fault or the run's' – which tells the agent exactly when to reach for it. No explicit when-not-to-use or named alternative (e.g. fastq_qc for raw read stats) is given.

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