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

io.github.tammy357/ts-second-opinion

by tammy357

write_orca_input

Write an ORCA transition-state optimisation input (wB97X-D4/def2-TZVP OptTS Freq) for a test reaction's recommended guess, returning the file paths and input text so you can run the DFT job.

Instructions

Write an ORCA TS-optimisation input (wB97X-D4/def2-TZVP OptTS Freq, as in GoFlow's tsopt.inp) for the recommended guess of a test reaction. Returns the file paths and input text.

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": "write_orca_input"
  }
}

Input Schema

NameRequiredDescriptionDefault
reaction_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

B3.4/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are supplied, so the description carries the full burden. It does disclose the operation is a write and that it returns both file paths and input text, which is useful, but it is silent on side effects an agent would care about: whether an existing file is overwritten, where on disk the file lands, and what happens if the reaction has no recommended guess.

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?

Two sentences, front-loaded with the action and the technical specification, with no filler. The 'as in GoFlow's tsopt.inp' clause is a compact and useful anchor rather than padding.

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 one-parameter file-writing tool with no output schema, the description adequately covers the return values in prose. It is still missing failure modes and output location, which matter for a tool whose primary effect is creating a file.

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% for the single reaction_id parameter, so the description must compensate. It adds the meaningful constraint that the id must refer to a test reaction possessing a recommended guess, but gives no format, range, or validation detail for the id itself.

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?

States a specific verb and resource — writes an ORCA TS-optimisation input — and pins down the exact level of theory (wB97X-D4/def2-TZVP, OptTS Freq) and the template it mirrors (GoFlow's tsopt.inp). It does not name a sibling or explicitly distinguish itself from adjacent tools like triage_reaction, so it falls short of a 5.

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?

'for the recommended guess of a test reaction' implies the precondition (a reaction that already has a recommended guess) and the context of use, but there is no explicit when-not guidance, no mention of what to call first to obtain that guess, and no stated alternative output formats.

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