Skip to main content
Glama
io.github.tammy357/ts-second-opinion

io.github.tammy357/ts-second-opinion

by tammy357

triage_batch

Triage many transition-state reactions at once from folders or CSV files, writing verdicts, recommended geometries, and ORCA inputs for focused DFT checks.

Instructions

Triage many reactions on disk at once. path: a folder with one sub-folder per reaction (reactant.xyz, product.xyz, the TS guess .xyz files, optional reaction.smi), or a .csv with columns id, reactant, product, guesses (and optional smiles, charge, multiplicity). Writes out_dir/verdicts.csv, the recommended geometry per reaction and ORCA inputs for reactions to check with DFT or re-generate. charge/multiplicity apply to reactions without a SMILES.

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": {
      "path": "<path>"
    },
    "name": "triage_batch"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
chargeNo
out_dirNotsso_batch
reportsNo
multiplicityNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.5/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 that the tool writes side-effect files to disk (out_dir/verdicts.csv, recommended geometries, ORCA inputs), which is real behavioral information. It omits overwrite/overwrite-existing behavior, whether out_dir is created or must exist, and any cost or runtime expectation for large batches — meaningful gaps for a bulk write tool.

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 dense and front-loaded: purpose first, then input formats, then outputs. The middle sentence listing CSV columns is a bit run-on but every clause carries concrete information. No filler sentences.

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?

There is no output schema, yet the description names the primary artifacts produced (verdicts.csv, recommended geometries, ORCA inputs), which covers most of what an agent needs. The unexplained 'reports' parameter and the absence of any note on what a 'verdict' contains keep it short of complete.

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 0%, so the description must compensate. It does well for path (both accepted formats and the expected CSV columns), out_dir (implied by 'Writes out_dir/verdicts.csv'), and charge/multiplicity (scoped to reactions without a SMILES). The 'reports' boolean parameter is never mentioned anywhere, leaving one of five parameters entirely undocumented.

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 opens with a specific verb and resource: 'Triage many reactions on disk at once,' which makes it distinguishable from the single-reaction sibling triage_reaction. It does not explicitly name an alternative, but the batch/'many reactions' framing is clear enough for an agent to know this is the bulk path.

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?

It explains how to supply input (a folder layout with one sub-folder per reaction, or a CSV with specific columns), which is useful operational guidance. However, it never says when to choose this over triage_reaction, triage_structures, or write_orca_input, nor what preconditions must hold before batch triage is appropriate.

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