Skip to main content
Glama

Lone Pair

Convert a structure file

convert
Read-onlyIdempotent

Convert a structure between formats: cdxml, cdx, mol, molV3, sdf, rxn, rxnV3, smiles, inchi, inchikey, cml, mrv, json (mol = V2000 molfile, molV3 = V3000, json = Lone Pair drawing). Reads ChemDraw CDXML and CDX. notes says what the target format cannot keep (for example dative bonds in a V2000 molfile). Refused, with the reason, instead of drawn wrongly: SMILES that cannot be read, aromatic rings that cannot alternate single and double bonds, and atoms with too many bonds (unless as_written).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "to": "<to>"
    },
    "name": "convert"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesThe format to write.
nameNoSet to true when `input` is a compound name (e.g. "aspirin") rather than a structure. The name is sent to PubChem to find the structure; this is the only network call the server makes. Default false.
inputNoThe structure as text: SMILES, reaction SMILES (reactants>agents>products), InChI, a molfile, RXN, SD file, CDXML, CML or Marvin text, or a Lone Pair drawing (the JSON from an earlier result, or the SVG text of an earlier figure).
as_writtenNoDraw atoms that have too many bonds instead of refusing the structure. Default false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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 readOnly, idempotent, non-destructive, open-world, so the safety profile is covered. The description adds real value beyond them: lossy-conversion reporting via `notes`, and an explicit refusal policy (SMILES that can't be read, unalternatable aromatic rings, over-bonded atoms) rather than silently drawing something wrong, with `as_written` as the escape hatch. It does not say what the response body looks like beyond `notes`, keeping it at a solid 3-4.

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?

Front-loaded with the core verb and format list, then behavior (notes, refusal). Every sentence carries information, though the long parenthetical format glossary and the trailing refusal clause make it dense for a single paragraph.

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?

No output schema exists, and the description compensates by explaining that `notes` reports what the target format cannot preserve. Combined with the format list and refusal policy, an agent has enough to call it correctly; only the broader response shape remains unspecified.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, but the description adds meaning the schema lacks: the format abbreviations (mol/molV3/json) are spelled out, and the refusal-by-default behavior is tied to `as_written` ('unless `as_written`'). The `name`/PubChem network-call nuance lives only in the schema, not the description.

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 ('Convert') and resource ('a structure') and enumerates the full source/target format set, including disambiguating the ambiguous ones (mol = V2000, molV3 = V3000, json = Lone Pair drawing). It does not explicitly contrast itself with the drawing/analysis siblings, but the format-conversion framing makes the distinction inferable.

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 rather than stated: the description explains what it reads (ChemDraw CDXML/CDX) and that `name` triggers a PubChem lookup only in the schema, but never says when to pick convert over draw/analyze/render_reaction, nor any prerequisites or ordering. An agent must infer the routing.

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