Skip to main content
Glama

Jean — Molecular Biology & Genomics

build_genbank_submission

Read-only

Turn a record into the SUBMISSION SET NCBI's table2asn consumes: a .fsa whose defline carries the source modifiers, and a 5-column feature table (.tbl) beside it.

Input Schema

NameRequiredDescriptionDefault
_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.
genbankYesthe record to submit, as GenBank text. Its features and topology are read from it — wire it from an export, or paste it.
_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.
mol_typeNoone of INSDC's two MANDATORY qualifiers on the source key. Omitting it lets table2asn choose, which is a scientific fact picked by a tool.genomic DNA
organismNothe scientific name of the source organism. `synthetic construct` is a real answer for a built vector, not an absence.synthetic construct
topologyNocircular for a plasmid. With this omitted table2asn writes `linear` into the LOCUS line, so a plasmid is deposited as a linear molecule with no error anywhere. Left empty, the record's own topology is used. Values: (From the record), circular (Circular), linear (Linear). Advanced.
geo_loc_nameNowhere the sample came from: a country, ocean or sea from the INSDC vocabulary, optionally `:region` and `, locality`. MANDATORY since December 2024, and it takes the same missing-value terms.missing: lab stock
collection_dateNowhen the sample was collected. MANDATORY on every GenBank submission since December 2024. `DD-Mmm-YYYY`, `Mmm-YYYY`, `YYYY`, an ISO form, or two of them separated by `/` for a range. A construct that was never collected anywhere takes an INSDC missing-value term such as `missing: lab stock`.missing: lab stock

Output Schema

NameRequiredDescriptionDefault
filesYesthe submission set: one entry per file, each with its `name` and `text`. The two names share a basename, which is how table2asn pairs them
changesYesevery feature the writer migrated, relabelled, refused or stripped a qualifier from, each with the authority's reason. Never empty-because-nothing-was-checked
commandYesthe exact table2asn invocation for the set, naming the submission template the user must make first
readingYeswhat the set is, generated from the record that was written rather than from the request
writtenYesfeatures written into the table. Branch on this rather than counting `changes`
problemsYeswhy the set cannot be submitted as it stands — an illegal collection date or a locality outside the vocabulary. Empty means the two mandatory modifiers are good, never that NCBI will be silent
featureTableYesthe `.tbl` alone, for pasting or diffing

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already establish readOnly/closed-world/non-destructive, and an output schema exists, so the bar is lower. The description's useful addition is that the result is a pair of files written beside each other with modifiers in the defline, but it says nothing about validation, failure modes, or whether anything is submitted to NCBI.

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?

A single front-loaded sentence with no filler; the artifact names are the most decision-relevant information and come first. Slightly dense, but every clause carries content.

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 rich schema, full parameter coverage, annotations, and an output schema, the description only needed to convey what the tool produces and the NCBI target — both are present. A note on how it relates to the ENA/AddGene builders would complete it.

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 coverage is 100% and the parameter descriptions already carry the real semantics (mandatory INSDC qualifiers, topology defaults, mol_type). The description adds nothing parameter-specific beyond the vague phrase 'source modifiers', so the 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+resource: turning a record into NCBI's table2asn submission set, and names the concrete artifacts (.fsa with source modifiers in the defline, plus a 5-column .tbl). The mention of NCBI/table2asn implicitly separates it from build_ena_submission and build_addgene_deposit, though no sibling is named outright.

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 only implied: NCBI/table2asn signals the GenBank route as opposed to ENA or AddGene, but the description never says when to pick this over build_ena_submission or build_addgene_deposit, nor any prerequisites (e.g. validated features, mandatory qualifiers).

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