Skip to main content
Glama

jean — Molecular Biology & Genomics

canonical_tautomer

Read-only

A small molecule's tautomers and the canonical one, as RDKit's TautomerEnumerator finds and scores them: 37 hydrogen-shift transforms (after MolVS and Sitzmann 2010), scored by aromatic rings, twelve weighted groups and hydrogens on P, S, Se and Te, ties to the smaller SMILES. Returns every tautomer, the canonical SMILES, the score and the 0-based atoms (implicit hydrogens, molfile order) a hydrogen moved between.

Input Schema

TableJSON 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.
_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.
moleculeYesthe structure: SMILES or a molfile.
max_tautomersNostop the enumeration at this many tautomers.
max_transformsNostop after this many transform applications.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
summaryYesthe enumeration in words, with the cap when one was reached
canonicalYesRDKit's canonical tautomer, as canonical SMILES
tautomersYesevery tautomer enumerated, as canonical SMILES, sorted

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior5/5

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

Annotations already mark this as a safe, non-destructive read operation. The description adds substantial behavioral context: the algorithm, the 37 hydrogen-shift transforms, scoring criteria, tie-breaking by smaller SMILES, and the exact atoms tracked between tautomers.

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 definition is two sentences with no wasted words and front-loads the purpose before technical details. The first sentence is dense with scoring and algorithm specifics, but those details are relevant to a complex cheminformatics tool.

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

Completeness5/5

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

Given the available output schema, 100% parameter coverage, and safety annotations, the description is complete enough for correct invocation. It explains the algorithm and return semantics without needing to repeat schema-level details.

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 every parameter. The description adds no syntax or format details for molecule, max_tautomers, max_transforms, _files, or _subject beyond what the schema provides, making the baseline of 3 appropriate.

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 specifies a concrete resource and action: finding a small molecule's tautomers and the canonical one via RDKit's TautomerEnumerator. It is clear what the tool does, but it does not explicitly distinguish itself from related sibling tools such as enumerate_protonation_states or compare_molecules.

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?

The description implies use for small-molecule tautomer enumeration but gives no explicit guidance on when to choose this tool over alternatives. There are no conditions, exclusions, or named sibling tools to route the agent.

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