Skip to main content
Glama

Jean — Molecular Biology & Genomics

draw_trace

Read-only

Draw a window of a Sanger read as an SVG figure: the four dye traces over their called bases, the per-base Phred bars and a base ruler.

Input Schema

NameRequiredDescriptionDefault
fromNofirst base drawn, 1-based and inclusive. Clamped into the read.
basesNohow many bases to draw. Keep it to a window you can read: past about 120 the peaks are narrower than the letters over them.
widthNofigure width. It SETS the per-base zoom for the window asked for, never crops it. In px.
_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.
paletteNowhich ink each dye is drawn in. `print` is the default here because the figure travels outside the app and onto white; `cvd` is the color-vision-deficiency-safe set. Values: classic (Classic (ABI)), cvd (Color-blind safe), print (Print (on white)).print
qualityNoprint the per-base Phred bars. A file with no confidence (many SCFs) draws none whatever this says.
_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.
documentNowhich trace file to draw: its name (`read_F.ab1`) or its project file id. A file id is project-specific, so a template ships this unset.
bases_rowNoprint the called bases between the ruler and the peaks. Advanced.
trace_heightNoheight of the peak band, under the ruler, quality and base rows. In px. Advanced.

Output Schema

NameRequiredDescriptionDefault
svgYesthe trace window as an SVG figure
readYesthe read drawn
widthYesfigure width in px
heightYesfigure height in px
lastBaseYeslast base drawn, 1-based inclusive
sequenceYesthe calls in the window drawn, so the picture and the string cannot disagree
firstBaseYesfirst base drawn, 1-based inclusive, AFTER clamping into the read
hasQualityYeswhether this file carries per-base confidence at all
meanQualityYesmean Phred over the window drawn, or 0 when the file carries no confidence — read `hasQuality` beside it rather than reading 0 as bad calls

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedOutput schema / properties / height / x-unit
      Added value: +"px"
    • addedOutput schema / properties / width / x-unit
      Added value: +"px"
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds that the output is an SVG figure with specific panels, which is useful, but it does not disclose additional behavior such as whether the figure is saved, returned inline, or how the window interacts with the read bounds.

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?

It is a single front-loaded sentence with no redundant wording. Every clause earns its place by naming the operation, input type, output format, and the visual elements produced.

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, full parameter descriptions, and annotations covering safety, the one-sentence description is nearly sufficient to call the tool correctly. It is slightly incomplete in not indicating sibling routing, such as when to use draw_trace versus export_trace or trace_raw_signal.

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 all ten parameters, including nested _subject and _files, are already documented. The description broadly corresponds to bases, quality, and bases_row but adds no parameter meaning beyond what the schema provides.

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?

The description states a specific verb and resource: 'Draw a window of a Sanger read as an SVG figure' and names the exact visual layers (dye traces, called bases, Phred bars, base ruler). It is distinguishable from most siblings, but it does not explicitly differentiate itself from adjacent tools such as export_trace or trace_raw_signal.

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?

Usage is implied by 'Draw a window,' but the description gives no explicit when-to-use guidance or exclusions relative to alternatives like export_trace, add_notebook_figure, or trace_raw_signal. The agent must infer that this is the visualization path rather than a data export or raw-signal tool.

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