Jean by Melad Labs

export_map_svg

Read-only

Render the open record's map to a publication SVG string, circular or linear — the same figure the Export panel draws, with the same knobs and the same defaults. Give it enzymes to draw the restriction sites. The linear layout can draw both strands' bases and a window of the record (start/end), which is the sequence view as a figure.

Input Schema

Name	Required	Description	Default
`end`	No	linear only: last base of the window to draw (1-based, inclusive); left unset, the record's last base. In bp. Only applies when layout is linear.
`font`	No	figure font — one of the three stacks that survive an SVG-to-PDF conversion without substitution.	sans
`size`	No	square canvas edge, before a legend strip is added below it. In px.
`start`	No	linear only: first base of the window to draw (1-based); left unset, the record's first base. In bp. Only applies when layout is linear.
`title`	No	figure title; left empty, the record's own name is used.
`_files`	No	The 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.
`layout`	No	circular: the ring; linear: the record unrolled into rows, features in lanes under a ruler and sites above it.	circular
`legend`	No	add a colour key on its own strip below the map.
`enzymes`	No	enzymes whose cut sites fill the site ring — resolved against the bundled cut catalog (REBASE spellings; smaller than the REBASE dossier the editor shows). Left unset, the run uses your active enzyme collection; with none active the ring is drawn empty rather than silently filled.
`_subject`	No	The 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.
`show_bases`	No	linear only: draw both strands' bases over the ruler; rows wrap to keep each base readable. Only applies when layout is linear.
`show_sites`	No	draw the outer restriction-site ring.
`show_labels`	No	draw each feature's name beside its arc.
`transparent`	No	omit the backing rect, so the figure drops onto any ground.
`collapse_duplicate_labels`	No	fold leader labels that would repeat a name into one row, as `misc_binding ×13` — the same rule the interactive map uses. Off reproduces the upstream renderer's figure exactly, one leader per feature.

Output Schema

Name	Required	Description
`svg`	Yes	publication SVG string
`rows`	Yes	rows a linear map wrapped into; 0 for the circular layout
`sites`	Yes	cut sites drawn (the outer ring, or the ticks above a linear map's ruler)
`width`	Yes	rendered width in px
`height`	Yes	rendered height in px — taller than the width when a legend strip was added

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 25, 2026
- addedOutput schema / properties / height / x-unit
```
Added value: +"px"
```
- addedOutput schema / properties / width / x-unit
```
Added value: +"px"
```

Changed7 schema fields changedOct 24, 2026

addedInput schema / properties / end

Added value: +{
+  "description": "linear only: last base of the window to draw (1-based, inclusive); left unset, the record's last base. In bp. Only applies when layout is linear.",
+  "minimum": 1,
+  "type": "number"
+}

addedInput schema / properties / layout

Added value: +{
+  "default": "circular",
+  "description": "circular: the ring; linear: the record unrolled into rows, features in lanes under a ruler and sites above it.",
+  "enum": [
+    "circular",
+    "linear"
+  ],
+  "type": "string"
+}

addedInput schema / properties / show_bases

Added value: +{
+  "default": false,
+  "description": "linear only: draw both strands' bases over the ruler; rows wrap to keep each base readable. Only applies when layout is linear.",
+  "type": "boolean"
+}

addedInput schema / properties / start

Added value: +{
+  "description": "linear only: first base of the window to draw (1-based); left unset, the record's first base. In bp. Only applies when layout is linear.",
+  "minimum": 1,
+  "type": "number"
+}

addedOutput schema / properties / rows

Added value: +{
+  "description": "rows a linear map wrapped into; 0 for the circular layout",
+  "type": "number"
+}

changedOutput schema / properties / sites / description

Previous value: -"cut sites drawn in the outer ring"New value: +"cut sites drawn (the outer ring, or the ticks above a linear map's ruler)"

changedOutput schema / required

Previous value: -[
-  "svg",
-  "width",
-  "height",
-  "sites"
-]New value: +[
+  "svg",
+  "width",
+  "height",
+  "sites",
+  "rows"
+]

First observedOct 20, 2026

TDQS

A4.2/5.0

Behavior4/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 adds useful behavior beyond that: it returns an SVG string, mirrors the Export panel's defaults, and explains that enzymes drive the restriction-site ring and that linear layout can render bases and a start/end window.

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 description is three sentences and front-loads the core action and output type. The remaining sentences add only the most relevant options, with no wasted preamble.

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 rich schema, annotations, and output schema, the description is complete enough for selection and invocation. It covers purpose, key layout behavior, enzyme handling, and linear-window semantics, though it does not discuss every optional knob because the schema already does that.

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 15 parameters in detail and carries the main burden. The description adds conceptual framing for enzymes, layout, show_bases, and the start/end window, but most of that meaning is already present in the schema descriptions.

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 states a specific verb and resource: render the open record's map to a publication SVG string, with circular or linear layouts. It clearly distinguishes the output as a figure like the Export panel draws, so an agent can identify the tool without opening the schema.

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?

The description gives clear context: use it to produce a publication SVG of the open record's map, optionally adding restriction sites or a linear sequence window. It does not explicitly name when not to use it or compare it against sibling export/drawing tools, so it stops short of full when/when-not guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Jean by Melad Labs tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?