Skip to main content
Glama
chemlit-kinetics-miner

chemlit-kinetics-miner

by WenNinghan

verify_speciation_kinetics

Verify acid-base speciation kinetics by checking Henderson-Hasselbalch consistency, catching pH/pKa column swaps and unphysical apparent rate constants.

Instructions

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.

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": {
      "ph": "<ph>",
      "pka": "<pka>",
      "k_ha": "<k_ha>",
      "k_a_minus": "<k_a_minus>"
    },
    "name": "verify_speciation_kinetics"
  }
}

Input Schema

NameRequiredDescriptionDefault
phYesExperimental aqueous pH.
pkaYesAcid dissociation constant pKa.
k_haYesIntrinsic protonated/acid species rate constant k_HA (M^-1 s^-1).
pka2NoOptional second dissociation constant pKa2 for diprotic compounds.
k_a_minusYesIntrinsic deprotonated/base species rate constant k_A- (M^-1 s^-1).
k_a2_minusNoOptional intrinsic rate constant of doubly deprotonated species (M^-1 s^-1).
tolerance_logNoMaximum allowed |log10(reported_k_app) - log10(predicted_k_app)|.
reported_k_appNoReported apparent second-order rate constant k_app(pH) in M^-1 s^-1.

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 does usefully disclose the check logic (alpha-weighted intrinsic rates, diprotic extension) and the failure modes it flags, but says nothing about whether the tool errors out or returns diagnostics, whether it mutates anything, or how pass/fail is signalled for a tool with no output schema.

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 with the verb first and the formula giving precision rather than filler. It is dense but efficient; nothing is clearly removable, though the parenthetical diprotic note is lightly compressed.

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?

For an 8-parameter verification tool with no annotations and no output schema, the definition explains the math adequately but leaves the result contract unspecified — an agent cannot tell whether to expect a boolean, a residual, or a list of flagged columns. That gap matters for a tool whose entire value is diagnostic output.

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 coverage is 100%, so every parameter including pka2, k_a2_minus, tolerance_log and reported_k_app is already documented. The description only notes the diprotic extension exists; it adds no formatting, unit, or tolerance semantics beyond the schema, so baseline 3 applies.

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?

Specific verb ('Verify') plus a precise resource ('acid-base speciation kinetics consistency') and the governing equation, so the agent knows exactly what computation this performs. It is implicitly distinct from the extraction and SMILES-validation siblings, but never names or contrasts them.

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 stated purpose: call it to cross-check reported k_app against Henderson-Hasselbalch predictions and catch column swaps. There is no explicit when-to-use, no when-not-to-use, and no mention of prerequisites such as which inputs must be measured versus estimated.

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