Skip to main content
Glama
chemlit-kinetics-miner

chemlit-kinetics-miner

by WenNinghan

validate_smiles_and_units

Validates compound names or raw SMILES with RDKit to catch valence and ring errors, while auditing rate-constant units, log10(k) parity, and diffusion limits.

Instructions

Validate a compound name / raw SMILES via RDKit (catching valence & broken-ring hallucinations, computing canonical SMILES, InChIKey, formula, exact MW, charge) and audit rate constant units, log10(k) parity, and Smoluchowski diffusion bounds.

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": {
      "compound_name": "<compound_name>",
      "k_value": "<k_value>"
    },
    "name": "validate_smiles_and_units"
  }
}

Input Schema

NameRequiredDescriptionDefault
phNoExperimental pH.
pkaNoCompound acid dissociation constant pKa.
k_unitsNoReported rate constant units (e.g. 'M^-1 s^-1', 'mM^-1 s^-1', 'M^-1 min^-1').M^-1 s^-1
k_valueYesNumeric rate constant value in reported units.
raw_smilesNoRaw SMILES string to sanitize and canonicalize.
compound_nameYesCompound common name or CAS number.
temperature_cNoExperimental temperature in degrees Celsius (°C).
reported_log10_kNoReported log10(k) for logarithmic cross-checking.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses what is checked and computed (valence and broken-ring hallucinations, canonical SMILES, InChIKey, formula, exact MW, charge, unit consistency, log10 parity, diffusion bounds), but it does not explain failure behavior, return format, or how results should be interpreted.

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 a single dense but well-structured sentence, front-loading the two main actions and using parentheticals to enumerate computed properties. It is efficient, though the parenthetical lists make it slightly harder to scan.

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?

The tool is complex with eight parameters, no annotations, and no output schema. The description covers the two validation domains and lists computed outputs, but it does not explain the return structure, error semantics, or how the audit results are presented, leaving an agent to infer behavior.

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 all eight parameters are already well documented in the input schema. The description references compound name, raw SMILES, rate constant units, and log10(k), but adds no parameter meaning beyond the schema.

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 states a specific dual purpose: validating a compound name or raw SMILES with RDKit, and auditing rate constant units, log10(k) parity, and Smoluchowski diffusion bounds. This is clear and concrete, though it does not explicitly distinguish itself from the sibling tools by name or scope.

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 by the validation and audit verbs, but there is no explicit guidance on when to use this tool versus alternatives such as verify_speciation_kinetics or extract_kinetics_records. No exclusions or preconditions are stated.

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