Skip to main content
Glama

jean — Molecular Biology & Genomics

write_structure_library

Read-only

Write a list of small molecules as one file: SDF (V2000 or V3000), each record named and, optionally, carrying its canonical SMILES and RDKit descriptors as data fields; or SMILES or CXSMILES, one record a line followed by its name. Written as RDKit's SDWriter, MolToSmiles and MolToCXSmiles write it; a structure RDKit cannot read is left out and its index returned.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
namesNoa name per structure, in the same order (the SDF title line, the SMILES second column).
_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.
formatNothe file format. Values: sdf (SDF), sdf-v3000 (SDF V3000), smiles (SMILES), cxsmiles (CXSMILES).sdf
_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.
moleculesYesthe structures: one SMILES or molfile per entry.
with_propertiesNoSDF only: add canonical_smiles and the RDKit descriptors to each record as data fields.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYesthe file
unreadYes0-based indices of the entries RDKit could not read, left out of the file
summaryYeshow many structures were written, of how many given, and which were left out

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior1/5

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

The annotations declare readOnlyHint=true, but the description explicitly says it writes a file, which is a mutating side effect. This is a direct contradiction, so the description fails to align with the structured safety hints.

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?

The description is front-loaded and covers key details in two sentences, but the second sentence is awkwardly phrased (‘Written as RDKit's SDWriter, MolToSmiles and MolToCXSmiles write it’) and slightly redundant.

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 tool's complexity (6 parameters, nested objects, output schema), the description covers formats, naming, optional properties, and error handling adequately. However, it omits permission requirements or side-effect details beyond the format specification.

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 parameters. The description adds minor context about naming and optional data fields but largely repeats what the schema provides.

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 (write) and resource (structure library file), specifying exact formats (SDF, SMILES, CXSMILES), record naming, and optional data fields. It clearly distinguishes this from read-only or search-oriented sibling tools by focusing on file output.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit guidance on when to use this tool versus alternatives like read_structure or search_molecule_library. The description only implies usage by describing output formats, without stating prerequisites or when-not-to-use conditions.

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