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

io.github.tammy357/ts-second-opinion

by tammy357

triage_reaction

Triage a single RDB7 reaction by running gated rules on all guesses, selecting consensus, mirror-repairing wrong-handed stereocentres, and returning a verdict with reasons and recommended TS geometry.

Instructions

Triage one RDB7 test reaction: run every gated rule on all 8 GoFlow guesses, pick the consensus among guesses that pass, repair a wrong-handed stereocentre by mirroring if that makes it pass, and return a verdict with reasons and the recommended TS geometry (xyz). score_against_reference adds D-MAE and stereo correctness against the reference DFT TS (evaluation only).

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": {
      "reaction_id": "<reaction_id>"
    },
    "name": "triage_reaction"
  }
}

Input Schema

NameRequiredDescriptionDefault
reaction_idYes
score_against_referenceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.8/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 behavioral burden. It usefully discloses the gated-rule execution, consensus among passing guesses, mirroring repair, and returned verdict plus TS geometry, but it does not clarify whether anything is persisted or modified, nor does it state read-only/destructive semantics or failure behavior.

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 front-loaded with the core action and proceeds through the pipeline in a logical order. The first sentence is dense, but every clause contributes relevant information and there is no filler.

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 a complex tool with no annotations and no output schema, the description covers the main computation and output type reasonably well. It still leaves gaps around prerequisites, failure/no-consensus behavior, side effects, and the exact verdict/xyz return structure.

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 0%, so the description must compensate. It explains score_against_reference well, including that it adds D-MAE and stereo correctness against the reference DFT TS for evaluation only, but reaction_id is only implied by 'one RDB7 test reaction' and receives no explicit format or lookup semantics.

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?

The description opens with a specific verb and scope: 'Triage one RDB7 test reaction.' It then details the internal consensus, stereocentre repair, and verdict/TS output, which clearly separates this single-reaction tool from batch-oriented siblings such as triage_batch.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It makes clear this is for triaging a single RDB7 test reaction and explains that score_against_reference is an evaluation-only mode. It does not explicitly say when to prefer triage_batch or triage_structures, but the single-reaction framing gives usable context.

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