Skip to main content
Glama

convert_chemistry

Convert chemistry and molecular files such as MOL, SDF, XYZ, SMILES, or PDB into JSON or CSV for downstream analysis and data processing.

Instructions

Convert chemistry/molecular file formats: MOL→JSON/CSV, SDF→JSON/CSV, XYZ→JSON, SMILES→JSON, PDB (molecular)→JSON. For advanced conversions, requires RDKit or Open Babel.

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": {
      "inputPath": "<inputPath>",
      "outputPath": "<outputPath>"
    },
    "name": "convert_chemistry"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputPathYesAbsolute path to input chemistry file
outputPathYesAbsolute path for output file (include extension)
inputFormatNoInput format (auto-detected if not provided)
outputFormatNoOutput format

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden, and it does disclose one real prerequisite: advanced conversions require RDKit or Open Babel. However, it never says which listed conversions are 'advanced' versus native, nor does it state whether outputPath is overwritten, how failures surface, or whether file size limits apply.

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 core purpose, with the arrow notation packing the supported conversions into minimal space. Nothing is redundant and the prerequisite caveat is properly placed second.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema and no annotations for a tool that writes files, so the description should say more about what is produced and what happens to an existing outputPath. The conversion matrix covers inputs well, but return behavior and overwrite semantics are unaddressed.

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 baseline is 3; the description's conversion matrix adds some constraint context on top of the format enums. It also creates mild ambiguity: the inputFormat enum includes mol2, cml, inchi, and json, but the prose lists only MOL, SDF, XYZ, SMILES, and PDB inputs, leaving unclear whether the unlisted enum values are actually supported.

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?

The description gives a specific verb plus a concrete domain ('Convert chemistry/molecular file formats') and enumerates the supported conversion matrix (MOL→JSON/CSV, SDF→JSON/CSV, XYZ→JSON, SMILES→JSON, PDB→JSON), so an agent can immediately tell this is a domain-specific format converter. It falls short of a 5 because it does not distinguish itself from adjacent siblings such as convert_biotech or convert_3d, which could plausibly touch overlapping molecular data.

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 by the domain: an agent infers 'use this when converting chemistry files.' There is no explicit when-to-use/when-not guidance and no named alternative among the many convert_* siblings, so routing between this and convert_biotech or batch_convert is left to inference.

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