Skip to main content
Glama
chemlit-kinetics-miner

chemlit-kinetics-miner

by WenNinghan

extract_kinetics_records

Extracts aqueous oxidation rate constants, experimental conditions, validated structures, and exact provenance spans from literature excerpts to produce traceable kinetics records.

Instructions

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.

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": {
      "text": "<text>"
    },
    "name": "extract_kinetics_records"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesScientific Markdown, LaTeX tabular, or OCR prose excerpt.
doc_idNoSource document identifier or DOI.MCP_DOC_01
page_numNo1-based page number.
pipeline_modeNoVerification depth ('full' runs Dual-Agent + RDKit + Physics Audit).full

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/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. It usefully discloses that provenance is exact character-offset EvidenceSpans and that 'full' runs Dual-Agent + RDKit + Physics Audit (via the schema), but it says nothing about cost/latency of that heavier mode, determinism, failure behavior on unparseable text, or whether any network/DB access occurs.

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?

A single front-loaded sentence that leads with the verb and the primary output before listing secondary fields. Dense and enumerative but every clause maps to an actual return field; slight run-on risk from the parenthetical oxidant list.

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, so the description appropriately enumerates the return payload (rate constants, conditions, identifiers, provenance offsets), giving the agent enough to know what it gets back. Remaining gap is behavioral — how mode choice affects output quality and how failures are reported.

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 all four parameters including the pipeline_mode enum and its meaning. The description adds no parameter-level detail beyond what the schema provides, which is the expected baseline 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

A specific verb ('Extract') plus an enumerated resource list: rate constants for four oxidant species, experimental conditions, canonical RDKit SMILES/InChIKey, and EvidenceSpan provenance. The output target is precise enough to separate it from verify_speciation_kinetics and validate_smiles_and_units, which by name handle verification rather than extraction.

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?

Implied usage is clear from 'from Markdown/LaTeX/OCR paper excerpts' — feed paper text, get structured kinetic records. But there is no explicit when-to-use/when-not guidance and no routing to the sibling tools (e.g., run validate_smiles_and_units before or instead of baselines).

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