io.github.tammy357/ts-second-opinion
Related Servers
Alternatives to io.github.tammy357/ts-second-opinion
No user-submitted related servers found.
Related Servers
- AlicenseBqualityCmaintenanceEnables LLM agents to run verified DFT materials workflows (structure fetch, relaxation, band/DOS) with automated convergence gates and physics validation, ensuring every result is machine-verified with a complete evidence trail.53MIT
- AlicenseBqualityCmaintenanceEnables auditable thermophysical data curation by validating molecules, predicting properties with JR-MPNN and UManSysProp, and normalizing, deduplicating, scoring, and triaging records with an audit trail.6GPL 3.0
- FlicenseBqualityDmaintenanceProvides computational chemistry tools for LLMs, enabling molecular operations like SMILES processing and geometry manipulation via a modular agent and tool system.9-
- AlicenseNot gradedqualityBmaintenanceProvides a local-first chemistry workbench for AI agents, enabling SMILES validation with human-readable diagnostics, molecule drawing, property calculation, format conversion, standardization, and batch cleaning via MCP.2MIT
- AlicenseBqualityCmaintenanceGives headless CAD agents a deterministic, dependency-free STL audit that checks manifoldness, plate grounding, single-shell structure, wall thickness, and normal orientation, returning a printable verdict with a critic score. Enables agents to gate and iteratively repair generated meshes before slicing or printing.3MIT
- FlicenseBqualityBmaintenanceA fail-closed MCP verification layer for DFT-to-MLIP workflows, gating Quantum ESPRESSO data ingestion, MACE/RuNNer dry-run command plans, model comparison, and reference validation behind scientific, software, and numerical checks with explicit PASS/WARN/FAIL/QUARANTINE/NOT_RUN statuses.8-
TDQS
Scored across 13 tools
Most tools target clearly different objects: triage (single RDB7 reaction vs. user structures vs. batch on disk), evaluation, calibration, rule authoring, ORCA export, and dataset audit. The main soft spot is overlap between triage_reaction, triage_structures, and evaluate_predictions, which all produce geometry/stereo comparisons against references, though the descriptions sharply distinguish dataset, inputs, and purpose.
Nearly all names follow a verb_noun pattern (list_reactions, triage_reaction, evaluate_predictions, gate_check aside, save_rule, write_orca_input, audit_rdb7_dataset). Deviations like gate_check (noun_verb) and benchmark_summary (noun phrase) are minor and still readable, so the convention is largely predictable.
13 tools sit comfortably in the well-scoped range for a specialized TS-triage server. Each tool maps to a distinct stage of the workflow—triage, evaluation, calibration, rule development, export, and data audit—with no filler entries.
The surface covers the full workflow: single/batch/arbitrary triage, stereo-aware evaluation, trust calibration, rule listing, source inspection, gating, saving, ORCA input writing, and dataset auditing. Minor gaps exist—no update/delete for saved rules and no explicit regenerate/repair tool—but agents can work around these via existing triage and rule tools.