chemlit-kinetics-miner
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| extract_kinetics_recordsA | Extract aqueous oxidation rate constants (O3, •OH, SO4•-, ClO•), experimental conditions (pH, T, pKa, water matrix), canonical RDKit SMILES/InChIKey, and exact character-offset EvidenceSpan provenance from Markdown/LaTeX/OCR paper excerpts. |
| validate_smiles_and_unitsB | 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. |
| verify_speciation_kineticsB | Verify acid-base speciation kinetics consistency using the Henderson-Hasselbalch law k_app(pH) = alpha_0k_HA + alpha_1k_A- (and diprotic extension), catching pH <-> pKa column swaps and unphysical apparent rate constants. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
The tools target mostly distinct pipeline stages: extraction, chemical/unit validation, and speciation consistency verification. There is some conceptual overlap between validate_smiles_and_units and verify_speciation_kinetics because both audit correctness, but their scopes are sufficiently separated by descriptions.
All tool names use snake_case and begin with a clear action verb (extract, validate, verify). The pattern is predictable and readable throughout.
Three tools are well-scoped for a focused extraction-and-validation pipeline. Each tool has a clear role, and there is no redundant surface area.
The core workflow is covered: extract kinetics records, validate structures/units, and verify speciation consistency. Minor gaps exist around literature retrieval, record export, deduplication, or broader kinetics validation, but agents can work around these.