jean — Molecular Biology & Genomics

export_map_svg

Read-only

Render the open plasmid's circular map to a publication SVG string — the same figure the Export panel draws, with the same knobs and the same defaults. Give it enzymes to draw the outer restriction-site ring.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`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.
`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.
`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_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

TableJSON Schema

Name	Required	Description
`svg`	Yes	publication SVG string
`sites`	Yes	cut sites drawn in the outer ring
`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.

First observedOct 20, 2026

TDQS

A3.8/5.0

Behavior3/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 meaningful context beyond them: the output matches the Export panel figure and honours 'the same knobs and the same defaults', which is a fidelity/reproducibility claim. It doesn't address whether the operation requires an open record or how large a figure is emitted, but the annotations carry the safety burden.

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?

Two sentences, front-loaded with the verb and resource, then one concrete behavioural hook. No filler or restatement of the name.

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 a 100% schema coverage and an output schema present, return values and parameter details are handled elsewhere, so the short description is nearly sufficient. The one soft spot is that it frames the input as 'the open plasmid' while the schema exposes _subject/_files for supplying records, leaving a minor ambiguity about which record is rendered.

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 11 parameters including defaults and enums; baseline is 3. The description only echoes the enzymes parameter ('Give it enzymes to draw the outer restriction-site ring'), adding no syntax or resolution detail beyond the schema.

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?

States a specific verb (render) and resource (the open plasmid's circular map) with a concrete output form (publication SVG string). The 'Export panel draws' framing further disambiguates it from sibling exporters like export_tree, export_trace, and draw_gel.

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 description implies usage context (rendering the open plasmid's figure at Export-panel fidelity) but names no alternatives and gives no when-not conditions. An agent must infer that this is the tool for circular plasmid figures rather than being routed explicitly.

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

All jean — Molecular Biology & Genomics 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?